Change Details

We need to determine what we are looking for hardware-wise in WDQS server.

We need to determine what we are looking for hardware-wise in WDQS server. **Requirements** //(from a [[ https://phabricator.wikimedia.org/T104879#1432540 | comment below ]])// 1. Running updates //fast// - i.e., much faster than the update stream - for comparison, labs machines do between 1 and 3 s of update stream per 1 s of clock time, but I'd like to have it on the level of 10s or so. 2. Running simple queries under 30 s. Yes, I know "simple" is not defined, so we'd have to kind of invent definition for it. 3. Being able to run several queries without noticeable performance degradation. I think for now since we don't have a lot of load values of several can be small, i.e. under 10, but in the future we may have higher reqs here. 4. Being able to run common WDQ queries within reasonable time (see T101528)

We need to determine what we are looking for hardware-wise in WDQS server. **Requirements** //(from a [[ https://phabricator.wikimedia.org/T104879#1432540 | comment below ]])// 1. Running updates //fast// - i.e., much faster than the update stream - for comparison, labs machines do between 1 and 3 s of update stream per 1 s of clock time, but I'd like to have it on the level of 10s or so. 2. Running simple queries under 30 s. Yes, I know "simple" is not defined, so we'd have to kind of invent definition for it. 3. Being able to run several queries without noticeable performance degradation. I think for now since we don't have a lot of load values of several can be small, i.e. under 10, but in the future we may have higher reqs here. 4. Being able to run common WDQ queries within reasonable time (see T101528)