2,684
edits
Line 31: | Line 31: | ||
JOBS=DEFPIX INTEGRATE CORRECT | JOBS=DEFPIX INTEGRATE CORRECT | ||
and run "xds_par" again. It completes after about 5 minutes on a fast machine, and we may inspect CORRECT.LP . | and run "xds_par" again. It completes after about 5 minutes on a fast machine, and we may inspect CORRECT.LP . | ||
== timings for processing sweep "e" as a function of MAXIMUM_NUMBER_OF_PROCESSORS and MAXIMUM_NUMBER_OF_JOBS == | == timings for processing sweep "e" as a function of MAXIMUM_NUMBER_OF_PROCESSORS and MAXIMUM_NUMBER_OF_JOBS == | ||
Line 63: | Line 64: | ||
total cpu time used 2833.4 sec | total cpu time used 2833.4 sec | ||
total elapsed wall-clock time 566.5 sec | total elapsed wall-clock time 566.5 sec | ||
but please note that this actually only uses 10 processors, since the default DELPHI=5 | |||
and the OSCILLATION_RANGE is 0.5°. | |||
Using | Using | ||
Line 82: | Line 85: | ||
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/sys/vm/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). | ||
== Comparison of XDS and published results of data processing == | == Comparison of XDS and published results of data processing == |