On Apr 27, 2009, at 8:40 PM, Paul D. Buck wrote:

Arg, the table did not come out ...

The table as HTML file and the logs both Raw, extracted, and extracted / sorted are available if anyone wants them.

Extracted looks something like this:

4/27/2009 3:06:16 PM            [cpu_sched_debug] enforce_schedule(): start
4/27/2009 3:06:16 PM [cpu_sched_debug] Request CPU reschedule: Core client configuration 4/27/2009 3:06:16 PM [cpu_sched_debug] Request enforce CPU schedule: schedule_cpus
4/27/2009 3:06:16 PM            [cpu_sched_debug] schedule_cpus(): start
4/27/2009 3:06:55 PM            [cpu_sched_debug] enforce_schedule(): start
4/27/2009 3:06:55 PM [cpu_sched_debug] Request enforce CPU schedule: Checkpoint reached
4/27/2009 3:07:38 PM            [cpu_sched_debug] enforce_schedule(): start
4/27/2009 3:07:38 PM [cpu_sched_debug] Request enforce CPU schedule: Checkpoint reached
4/27/2009 3:08:39 PM            [cpu_sched_debug] enforce_schedule(): start
4/27/2009 3:08:42 PM            [cpu_sched_debug] enforce_schedule(): start


Extracted / Sorted looks something like this:

04/27/09 17:28:17||[cpu_sched_debug] enforce_schedule(): start
04/27/09 15:39:35||[cpu_sched_debug] enforce_schedule(): start
04/27/09 17:25:15||[cpu_sched_debug] Request CPU reschedule: application exited 04/27/09 18:12:57||[cpu_sched_debug] Request CPU reschedule: application exited 04/27/09 17:33:28||[cpu_sched_debug] Request CPU reschedule: application exited 04/27/09 15:15:08||[cpu_sched_debug] Request CPU reschedule: Core client configuration 04/27/09 15:35:30||[cpu_sched_debug] Request CPU reschedule: files downloaded 04/27/09 18:12:58||[cpu_sched_debug] Request CPU reschedule: handle_finished_apps 04/27/09 17:25:15||[cpu_sched_debug] Request CPU reschedule: handle_finished_apps 04/27/09 17:33:28||[cpu_sched_debug] Request CPU reschedule: handle_finished_apps 04/27/09 15:22:43||[cpu_sched_debug] Request CPU reschedule: Idle state change 04/27/09 18:23:13||[cpu_sched_debug] Request CPU reschedule: Idle state change 04/27/09 18:22:52||[cpu_sched_debug] Request enforce CPU schedule: Checkpoint reached 04/27/09 18:17:58||[cpu_sched_debug] Request enforce CPU schedule: Checkpoint reached


Note the examples are from different systems


     Xeon 32 Xeon 64 Mac Pro Q9300 i7
   enforce_schedule(): start 241 387 272 262 407
   Request CPU reschedule: application exited 3 11 14 22 19
   Request CPU reschedule: Core client configuration 1 1 1 1 1
   Request CPU reschedule: files downloaded 1 9 15 26 21
   Request CPU reschedule: handle_finished_apps 3 11 14 22 19
   Request CPU reschedule: Idle state change 2 2 2 2 6
   Request CPU reschedule: Scheduling period elapsed 0 4 0 0
   Request enforce CPU schedule: Checkpoint reached 86 379 129 92 302
   Request enforce CPU schedule: schedule_cpus 7 17 25 47 44
   schedule_cpus(): start 7 17 25 48 44

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to