You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

Numbers are in hours


Large data set VLASS1.2.sb36491855.eb36574404.58585.53016267361_datacolumn.ms with full parameters and copying cfcache to local disk at CHTC.

StepNRAO (steps-all-parallel9)NRAO/CHTC (steps-all-parallel17)NRAO/AWS (steps-all-parallel16)
019.427.7 (ran at CHTC)12.3
0560.2
65.9
0624
24.4
0711.8
21.4
1555.2
58.9
166.1
7.6
23230.8

2446

Total443.5

Small data set test.ms with full parameters and not copying cfcache to local disk at CHTC using the 16k (wrong) cfcache

StepNRAO (steps-all-parallel12)NRAO/CHTC (steps-all-parallel15)NRAO/AWS (steps-all-parallel14)
011.82.01.9
058.656.85.1
063.03.92.0
072.02.32.2
156.956.34.3
161.41.71.4
238.347.85.3
2414.166.016.8
Total46.1226.839.0


CPUs at CHTC are noticibly slower than CPUs at NRAO.  For example, their set of c20xx machines (e20{03..18}) each have two Intel Xeon Silver 4114 2.20GHz processors and 0.5TB to 1TB of memory, while their large memory machines (mem3, mem2001, mem2002) each have four Intel Xeon E7-4820 v4 2.00GHz processors and 2TB to 4TB of memory.  Possible reasons for this slowdown:

  • cfcache on cephfs
  • Slower CPUs
  • Multiple users
  • Hyperthreading

I ran a small data set test with full parameters at CHTC that copied cfcache from /staging to local disk and step05 took only 16.7 hours instead of the 56.8 hours it had taken using cfcache on /staging.


Small data set test.ms with full parameters and not copying cfcache to local disk at CHTC using the 8k (right) cfcache and copying the cfcache to local disk at CHTC.

StepNRAONRAO/CHTC (steps-all-parallel19)NRAO/AWS
01


05


06


07


15


16


23


24


Total


  • No labels