dragnet:benchmarks_of_the_lotaas_pipelines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dragnet:benchmarks_of_the_lotaas_pipelines [2016-08-09 15:03] – [rfifind benchmarks] Sotiris Sanidasdragnet:benchmarks_of_the_lotaas_pipelines [2017-03-08 15:27] (current) – external edit 127.0.0.1
Line 71: Line 71:
 ==== Benchmarks for filterbank creation with psrfits2fil ==== ==== Benchmarks for filterbank creation with psrfits2fil ====
  
-A series of tests were ran on dragnet (drg01), directly (now through slurm), on fits files from a random LOTAAS observation. Number of cores,means number of different fits files processed simultaneously. The total time is an extrapolation of this benchmark.\\ 
  
-Only one test was ran for each occasion. Repeating them showed differences in execution time, but I doubt that the results change qualitatively.+psrfits2fil was executed with different numbers of parallel processes. The following plot shows the amount of time needed in order to create the fil files for various cases of parallel psrfits2fil instances.\\
  
-=== Input/Output on the same disk === +Using the same disk the following cases were tried: 1,3,4,5,8,12,16. Anything above 16 is just an extrapolation\\ 
-1-core:354sec\\ +for 2 disks: 1,4,8,12,16,20,24,28,32
-Total time for 16 files:5664sec\\+
  
-3-cores:630sec\\ +{{dragnet:benchmarks:psrfits2fil1a.png?400}}
-Total time for 16 files:3360sec\\+
  
-4-cores:720sec\\ +Using multithreading with 2 disks, gives a smooth linear performance up to 24 cores, and then it turns slightly worse, probably due to I/O.
-Total time for 16 files:2880sec\\+
  
-5-cores:1106sec\\ +Using the above results, I extrapolated the time needed with each work strategy in order to compute 32 filtebanks.\\
-Total time for 16 files:3539sec\\+
  
-8-cores:1735sec\\ +{{dragnet:benchmarks:psrfits2fil1b.png?400}}
-Total time for 16 files:3360sec\\+
  
-16-cores:3778sec\\ +When using the same disk, the fastest execution time is achieved having 4 psrfits2fil instances running in parallel. Above that, probably disk I/O normalises all the results and the performance decreases gradually, probably due to the increased I/O calls, since the throughput must already be saturated.\\
-Total time for 16 files:3778sec\\+
  
-When writing the filterbank in the same disk with the fits file, the best performance is achieved by having 4 psrfits2fil instances running.  +Using 2 disks, the performance is significantly better, and the best results are achieved using 24 psrfits2fil instances in parallel, although the difference remains small.\\
- +
-=== Input/output on different disks === +
-1-core:329sec\\ +
-Total time for 16 files:5264sec\\ +
- +
-4-cores:523sec\\ +
-Total time for 16 files:2092sec\\ +
- +
-8-cores:901sec\\ +
-Total time for 16 files:1802sec\\ +
- +
-16-cores:1513sec\\ +
-Total time for 16 files:1513sec\\ +
- +
-24-cores (hyperthreaded):2252sec scales perfectly!\\ +
-32-cores (hyperthreaded):3346sec performance loss already evident;~340 sec slower than expected +
- +
-Using all the cores in the dragnet nodes gives the best performance. Moreover, hyperthreading behaves exactly as having the extra cores. +
- +
-Moving a fil file from /data2 to /data1 takes 1 minute. +
  
 ==== rfifind benchmarks ==== ==== rfifind benchmarks ====
Line 129: Line 102:
 {{dragnet:benchmarks:rfifind1b.png?400}} {{dragnet:benchmarks:rfifind1b.png?400}}
 {{dragnet:benchmarks:rfifind2b.png?400}} {{dragnet:benchmarks:rfifind2b.png?400}}
 +
 +From the above, we can conclude that using 1 or 2 disks does not make a big difference. Also, hyperthreading works smoothly, and indeed the best strategy is to have the maximum possible number of rfifind instances running in parallel.
 +
 +==== Cartesius Benchmarks ====
 +
 +Processing 1 full pointing on cartesius using either /dev/shm or HDDs
 +
 +{{dragnet:benchmarks:cartesius_bm1.png?400}}
  • Last modified: 2016-08-09 15:03
  • by Sotiris Sanidas