Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong cached queries test parameters #3804

Closed
volyrique opened this issue May 31, 2018 · 1 comment · Fixed by #4601
Closed

Wrong cached queries test parameters #3804

volyrique opened this issue May 31, 2018 · 1 comment · Fixed by #4601

Comments

@volyrique
Copy link
Contributor

The documentation states that the parameter values for the cached queries test are 1, 10, 20, 50, and 100; these were also the values used in run 8de314d3-b970-4295-a3ca-3682f3905a3b (the last one before the test became broken). However, the last successful run uses 16, 32, 64, 128, 256, and 512. Is that intentional?

@zloster
Copy link
Contributor

zloster commented Mar 25, 2019

(Several months later)...
https://tfb-status.techempower.com/unzip/results.2019-03-16-06-30-33-053.zip/results/20190312173754/ulib-postgres/cached_query/raw.txt
The problem is still here.
Also only the 16 queries test case is not able to saturate the 10 Gb/s network. All the other (32, 64, 128, 256, 512) are hitting the transfer limit of 1.08-1.09 GB/s.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants