CRwiki

User Tools

Site Tools

Trace:
tcr_sri002

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tcr_sri002 [2020/04/26 12:13] – tmatejuktcr_sri002 [2023/08/01 01:08] (current) – external edit 127.0.0.1
Line 36: Line 36:
 ==== sbatch example ==== ==== sbatch example ====
 Use Quantum Espresso 6.5. This description assumes that path to binaries is ''/home/users/${USER}/soft/qe-6.5/bin'' . Use bellow ''qe-test.sbatch'' file to run computation. Use Quantum Espresso 6.5. This description assumes that path to binaries is ''/home/users/${USER}/soft/qe-6.5/bin'' . Use bellow ''qe-test.sbatch'' file to run computation.
 +  #!/bin/bash -l
   #SBATCH --job-name="qe-test_N2_n32"   #SBATCH --job-name="qe-test_N2_n32"
   #SBATCH --nodes=2                   # number of computing_nodes   #SBATCH --nodes=2                   # number of computing_nodes
Line 47: Line 47:
      
   WORKDIR="/home/users/${USER}/soft_tests/qe_run_`date +%s`_${RANDOM}/"   WORKDIR="/home/users/${USER}/soft_tests/qe_run_`date +%s`_${RANDOM}/"
-  mkdir -p ${WORKDIR} +  mkdir -p ${WORKDIR} 
 +  cd ${WORKDIR} 
 +  
   export BIN_DIR="/home/users/${USER}/soft/qe-6.5/bin"   export BIN_DIR="/home/users/${USER}/soft/qe-6.5/bin"
   export PATH=${BIN_DIR}:$PATH   export PATH=${BIN_DIR}:$PATH
   export PSEUDO_DIR=${WORKDIR}   export PSEUDO_DIR=${WORKDIR}
   export TMP_DIR="/tmp"   export TMP_DIR="/tmp"
-   +     
-  mkdir -p ${WORKDIR} +
-  cd ${WORKDIR} +
   #copy input files and pseudo files to ${WORKDIR}    #copy input files and pseudo files to ${WORKDIR} 
   cp /home/users/${USER}/downloads/quantum_espresso_input_files/* ${WORKDIR}   cp /home/users/${USER}/downloads/quantum_espresso_input_files/* ${WORKDIR}
Line 70: Line 70:
 Bellow results show time of computation in function of used resources (computation scalability) for a specific computational task done with ''pw.x'' program. Bellow results show time of computation in function of used resources (computation scalability) for a specific computational task done with ''pw.x'' program.
  
-Assigning a larger amount of computing nodes does not always lead to a (efficient) reduction in computing time (wall-time of the job). To find the most appropriate number of nodes for a specific type of job, it is essential to run one's own benchmarks. In general, parallel jobs should scale to at least 70% efficiency for the sake of other TCR users. <color #22b14c>One user using twice the resources to squeeze out 10% more performance may be keeping other users from working at all</color>.+Assigning a larger amount of computing nodes does not always lead to a (efficient) reduction in computing time (wall-time of the job). To find the most appropriate number of nodes for a specific type of job, it is essential to run one's own benchmarks. In general, parallel <color #22b14c>jobs should scale to at least 70% efficiency for the sake of other TCR users</color>. One user using twice the resources to squeeze out 10% more performance may be keeping other users from working at all.
  
 Bellow results should be consider as results of this specific computational task on this specific hardware (TCR cluster) and not overall benchmark for Quantum Espresso software suite. Bellow results should be consider as results of this specific computational task on this specific hardware (TCR cluster) and not overall benchmark for Quantum Espresso software suite.
tcr_sri002.1587896024.txt.gz · Last modified: 2023/08/01 06:38 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki