2,652
edits
2VB1: Difference between revisions
→timings for sweep "e", and optimal MAXIMUM_NUMBER_OF_PROCESSORS and MAXIMUM_NUMBER_OF_JOBS
(start work) |
|||
| Line 13: | Line 13: | ||
For all the sweeps, processing stopped with the usual error message after the IDXREF step. | For all the sweeps, processing stopped with the usual error message after the IDXREF step. | ||
== timings for sweep "e" | == timings for processing sweep "e" as a function of MAXIMUM_NUMBER_OF_PROCESSORS and MAXIMUM_NUMBER_OF_JOBS == | ||
The following is going to be rather technical! If you are only interested in crystallography, skip this. | The following is going to be rather technical! If you are only interested in crystallography, skip this. | ||
| Line 42: | Line 42: | ||
MAXIMUM_NUMBER_OF_JOBS=1 ! the default | MAXIMUM_NUMBER_OF_JOBS=1 ! the default | ||
the times are | the times are | ||
total cpu time used 2833.4 sec | |||
total elapsed wall-clock time 566.5 sec | |||
Using | Using | ||
| Line 61: | Line 62: | ||
MAXIMUM_NUMBER_OF_PROCESSORS=4 | MAXIMUM_NUMBER_OF_PROCESSORS=4 | ||
MAXIMUM_NUMBER_OF_JOBS=6 | MAXIMUM_NUMBER_OF_JOBS=6 | ||
performs best for a 2-Xeon X5570 machine with 24GB of memory and a RAID1 consisting of 2 1TB SATA disks. It should be noted that the dataset has 27GB, and in 296 seconds this means 92 MB/s continuous reading. The processing time is thus limited by the disk access, not by the CPU. And no, the data are not simply read from RAM (tested by "echo 3 > /proc/drop_caches before the XDS run). | performs best for a 2-Xeon X5570 machine with 24GB of memory and a RAID1 consisting of 2 1TB SATA disks. It should be noted that the dataset has 27GB, and in 296 seconds this means 92 MB/s continuous reading. The processing time is thus limited by the disk access, not by the CPU. And no, the data are not simply read from RAM (tested by "echo 3 > /proc/sys/vm/drop_caches before the XDS run). | ||