April 25, 2018 Dataset Open Access

Kelling, Jeffrey; Juckeland, Guido

Citation Style Language JSON Export

{
  "id": "16", 
  "title": "Profiling of RT-PICLS Code", 
  "author": [
    {
      "family": "Kelling, Jeffrey"
    }, 
    {
      "family": "Juckeland, Guido"
    }
  ], 
  "type": "dataset", 
  "publisher": "Rodare", 
  "DOI": "10.14278/rodare.16", 
  "issued": {
    "date-parts": [
      [
        2018, 
        4, 
        25
      ]
    ]
  }, 
  "abstract": "<p>It was observed, that the RT-PICLS code ran by FWKT on the hypnos cluster was producing an unusual amount of system load, according to Ganglia metrics. Since this may point to an IO-problem in the code, this code was analyzed more closely.</p>\n\n<p>RT-PICLS was run with additionally provided input data on 64 CPU cores (AMD Opteron) in a single node of the hypnos cluster. Score-P 4.0 with IO-tracing support was used for profiling and tracing of the application. A developer version of Vampir 9.2 [3] enabled graphical analysis of the traces.</p>\n\n<p>Different file systems were evaluated for storing the output:</p>\n\n<ul>\n\t<li><strong>bigdata</strong>: the high-performance file system of the cluster based on GPFS.</li>\n\t<li><strong>nfs</strong>: a loop-mounted EXT4 image mounted to the current compute node via NFS.</li>\n\t<li><strong>scr</strong>: the local scratch file-system of the compute node.</li>\n\t<li><strong>tmpfs</strong>: a virtual filesystem, physically located in the main memory of the compute node.</li>\n</ul>\n\n<p>The trace files that were used to compile the referenced report are collected in this upload.</p>"
}