You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Michael Spiegel (JIRA)" <ji...@apache.org> on 2010/03/18 21:54:27 UTC
[jira] Updated: (CASSANDRA-905) improve stress_py termination
condition
[ https://issues.apache.org/jira/browse/CASSANDRA-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Spiegel updated CASSANDRA-905:
--------------------------------------
Attachment: CASSANDRA-905.patch
The patch that changes the sleep cycle of stress.py to 0.1 second intervals.
> improve stress_py termination condition
> ---------------------------------------
>
> Key: CASSANDRA-905
> URL: https://issues.apache.org/jira/browse/CASSANDRA-905
> Project: Cassandra
> Issue Type: Improvement
> Components: Contrib
> Affects Versions: 0.6
> Reporter: Michael Spiegel
> Priority: Minor
> Attachments: CASSANDRA-905.patch
>
>
> Currently the stress.py script will sleep every (progress_interval) seconds and then check for termination. This can be confusing when trying to accurately use timing statistics based on the execution duration of the script. For example, if progress interval is 10 seconds then the script is guaranteed to terminate after N seconds, where N is some multiple of 10. I've attached a patch where the script sleeps every 0.1 seconds, and does a poll to see if the correct interval has passed in order to print information. The patch also ensures that statistics will be reported at the completion of the worker threads.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.