| | 141 | === 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. |
| | 143 | 2. ... 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). |
| | 146 | |
| | 147 | |
