Changes between Version 62 and Version 63 of benchmarks

Show
Ignore:
Timestamp:
11/21/11 16:03:40 (9 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • benchmarks

    v62 v63  
    140140 
    141141=== Notes === 
    142 1. The machine where CREAM (gLite) was running, had more resources (in particular CPU cores and virtual memory) than the machines with QCG and UNICORE. 
     1421. The machine where CREAM (gLite) was running had more resources (in particular CPU cores and virtual memory) than the machines with QCG and UNICORE. 
    1431432. ... hovewer this machine was additionally loaded by external tasks (about 500-2000 tasks - the tests were performed by 2 weeks). 
    144 3. QCG returns the job status when the job is already in queueing system, gLite and UNICORE not necessarily. Thus, e.g. in the throughput tests, new tasks appeared after the test finish). 
    145 4. The bottle-neck (especially in the second group of tests) was the throughput of the WP4 partition and Maui which imposed that only 64 tasks could be scheduled per one scheduling cycle (at least 3.5 minutes). 
     1443. QCG returns the job status when the job is already in queueing system, gLite and UNICORE not necessarily. Thus, e.g. in the throughput tests, new tasks appeared after the test finished. 
     1454. The bottle-neck (especially in the second group of tests) was the throughput of the WP4 partition and Maui, which imposed that only 64 tasks could be scheduled per one scheduling cycle (at least 3.5 minutes). 
    146146 
    147147