[Erp5-report] r8424 - /erp5/trunk/utils/erp5mechanize/runBenchmarks.py

nobody at svn.erp5.org nobody at svn.erp5.org
Wed Jul 12 14:36:47 CEST 2006


Author: vincent
Date: Wed Jul 12 14:36:44 2006
New Revision: 8424

URL: http://svn.erp5.org?rev=8424&view=rev
Log:
Sleep before probing threads : there is few chance that a thread could have data available right away, and this will same some time when the last thread is finished.

Modified:
    erp5/trunk/utils/erp5mechanize/runBenchmarks.py

Modified: erp5/trunk/utils/erp5mechanize/runBenchmarks.py
URL: http://svn.erp5.org/erp5/trunk/utils/erp5mechanize/runBenchmarks.py?rev=8424&r1=8423&r2=8424&view=diff
==============================================================================
--- erp5/trunk/utils/erp5mechanize/runBenchmarks.py (original)
+++ erp5/trunk/utils/erp5mechanize/runBenchmarks.py Wed Jul 12 14:36:44 2006
@@ -175,6 +175,7 @@
   [thread.start() for thread in thread_list] # Start all threads at 'once'.
 
   while len(thread_list):
+    sleep(5) # Sleep to leave more cpu time for actual tests.
     for pos in xrange(len(thread_list)-1, -1, -1): # From last to first, to be able to delete objects while looping.
       thread = thread_list[pos]
       thread_name = thread.getName()
@@ -210,7 +211,6 @@
       if not thread.isAlive():
         print '%s: Test thread %s ended.' % (time(), thread.getName(), )
         del thread_list[pos] # This thread won't move anymore, throw it.
-      sleep(5) # Sleep to leave more cpu time for actual tests.
 
   # Post processing of load computation : as threads can produce results in any order, we must wait for everything to be finished to compute the load.
   for server, server_load in server_load_list.items():




More information about the Erp5-report mailing list