このページの更新は終了しました。

最新の情報はTSUBAME3.0計算サービスのWebページをご覧ください。

TSUBAME2.5からTSUBAME3.0へのデータ移行方法の資料はこちら

After 2014 summer maintenance, the program has become slow. ? (2014/8/20 new)

It may be slower execution environment and compilation environment is not met. 
I tried to experiment below. I'll try to compile running in (SP3) the current environment first.

> ifort -V
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on Intel(R) 64,
 Version 14.0.2.144 Build 20140120
> which ifort
/usr/apps.sp3/isv/intel/xe2013.1.046/composer_xe_2013_sp1.2.144/bin/intel64/ifort
> cp -f /work0/soudan/tune .
> cd tune
> icc -c wclock.c
> ifort -fast -o sample2 sample2.f wclock.o
> ./sample2
  TIME=    5.32620000839233        1586700028.46718     

Next, I want to enable the path of the old environment (SP1)

> . /usr/apps/isv/intel/xe2013.1.046/bin/ifortvars.sh intel64
> ./sample2
  TIME=    5.36028885841370        1586700028.46718     
> . /usr/apps/isv/intel/xe2012/bin/ifortvars.sh intel64
> ./sample2
  TIME=    7.71737718582153        1586700028.46718     

It seems that even if you run the same way, but thank you to run Align the environment.

I've prepared the shell to check the path of the execution environment. 
I use as follows.

1.check the work environment
> pathcheck
>
Nothing is displayed if there is no problem.

"command-not-found " When you see, Specify the full path
> /usr/apps.sp3/free/bin/pathcheck

If the error of the old environment is displayed.
/usr/apps/isv/intel/xe2013.1.046/composer_xe_2013_sp1.2.144/bin/intel64 in PATH may cause error or performance degradation
/usr/apps/isv/pgi/14.6/linux86-64/2014/libso in LD_LIBRARY_PATH may cause error or performance degradation
For more details, please refer ....

This may have left a description of the path to .bashrc etc.. 
Please double-check your environment specified.

2.Confirmation of the batch shell
You modified as follows: the shell of the batch.

  :
pathcheck
# mpirun -n 32 -hostfile $PBS_NODEFILE ./sample11
  :

Please submitted the job in the select=1. 
It is OK if you do not see anything to the standard output. 
If an error such as the number 1 to the standard output is displayed 
Please double check the path settings in the shell.