-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
StatusThread should wake up when the test has completed and exit. #316
Comments
Closed
allanbank
added a commit
to allanbank/YCSB
that referenced
this issue
Jul 16, 2015
completing via a CountDownLatch. Fixes brianfrankcooper#316
allanbank
added a commit
to allanbank/YCSB
that referenced
this issue
Jul 17, 2015
client (worker) thread completing via a CountDownLatch. Fixes brianfrankcooper#316
allanbank
added a commit
to allanbank/YCSB
that referenced
this issue
Jul 17, 2015
client (worker) thread completing via a CountDownLatch. Fixes brianfrankcooper#316
allanbank
added a commit
that referenced
this issue
Jul 18, 2015
Shutdown the status thread as soon as clients complete (Issue #316)
Closed
Closed
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
client (worker) thread completing via a CountDownLatch. Fixes brianfrankcooper#316
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
Shutdown the status thread as soon as clients complete (Issue brianfrankcooper#316)
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
client (worker) thread completing via a CountDownLatch. Fixes brianfrankcooper#316
jaricftw
pushed a commit
to jaricftw/YCSB
that referenced
this issue
Jul 19, 2016
Shutdown the status thread as soon as clients complete (Issue brianfrankcooper#316)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre 0.2.0-rc2 the YCSB benchmark would exit as soon as all of the operations had completed. This allowed users to use the wall clock time as a coarse grain benchmark across runs. For instance I have several scripts to run YCSB across changes in the MongoDB driver. I use the wallclock time for each run to know if there are any regressions. Now all runs finish in 20 seconds regardless of the actual time to complete operations.
With 0.2.0-rc2 the StatusThread is keeping the ycsb client alive until the StatusThread does a poll after the all of the operations had completed. Thread dump below that show the only two remaining threads are the main which is in a Thread.join and the StatusThread which is in a sleepUnitl().
The text was updated successfully, but these errors were encountered: