In order to test MKLNP, HTTNP and httfix for the case of dirscf=.t.
I used Firefly71G and a PC(Win7) having the following CPU (This PC is different one
for the title of " 8 cores +HTT").
CPU Brand String : Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
CPU Features : CMOV, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2,
HTT, MWAIT, EM64T
actual # of cores/package : 4
actual # of threads/package : 8
actual # of threads/core : 2
From this list, it is known that the number of physical cores is 4,
then KMLNP=4 and HTTNP=2. Moreover, I chose httfix=.f. Next, I made four
nodes on the c drive.
c:\node1 c:\node2 c:\node3 c:\node4
Under the above condition, I confirmed that wall-clock time reduced to
less than a third (i.e.1/3) of the single-node calculation, although
the four nodes were generated on the one HD. This is unexpected matter
for me, because I have recognized that parallel calculations of Firefly
require a separate HD for each node. Maybe, use of separate HD is necessary
for the case of dirscf=.f. (i.e disk I/O mode).