Can you post static_tov.out? How do you know only one core is used? From top/a system monitor?
-- Ian Hinder http://members.aei.mpg.de/ianhin > On 5 May 2017, at 04:08, Robert Kopp <[email protected]> wrote: > > I directly edited the *.ini file so that ppn=4, max-num-threads=4, > num-threads=4. The run yielded correct results, however, it took the same > amount of time (about six hours), and apparently used only one thread. This, > despite the fact that the multiple cores are recognized (static_tov.out). > This leaves me wondering if there is anything else I can do to get the > multiple cores used to speed up the computation process. > > > > > On Thursday, May 4, 2017 12:52 AM, Ian Hinder <[email protected]> wrote: > > > > On 3 May 2017, at 18:22, Robert Kopp <[email protected]> wrote: > > > Do you suppose this could be the problem? > > > > # Source tree management > > sourcebasedir = /home/robert > > optionlist = > > /home/robert/Cactus/repos/simfactory2/mdb/optionlists/ubuntu.cfg > > submitscript = generic.sub > > runscript = > > /home/robert/Cactus/repos/simfactory2/mdb/runscripts/debian.sh > > make = make > > basedir = /home/robert/simulations > > ppn = 1 > > max-num-threads = 1 > > num-threads = 1 > > nodes = 1 > > I think you need to change ppn to 4 and max-num-threads to 4. If you usually > want to run on 4 threads, you could also change num-threads to 4. You can > edit the file directly. > > Erik, is "sim setup" supposed to set these automatically for the current > machine, or is the user supposed to edit the file? > > > > > > > > ~/Cactus/simfactory/mdb/machines/robert-desktop.ini > > > > If so, would I change this file directly, or try to override it some other > > way? > > > > > > > > On Wednesday, May 3, 2017 12:51 AM, Ian Hinder <[email protected]> > > wrote: > > > > > > > > On 3 May 2017, at 05:23, Robert Kopp <[email protected]> wrote: > > > > > The message I sent a little earlier with a file attachment may not reach > > > the list because of its size, 600K or more (includes all the data points > > > in the simulation). Perhaps this will be enough to determine the source > > > of the problem, though--at least, for someone with experience with this > > > application. Otherwise I'll try to reduce the size of the attachment to > > > <60K and find the relevant portions. > > > > > > INFO (Carpet): MPI is enabled > > > INFO (Carpet): Carpet is running on 1 processes > > > INFO (Carpet): This is process 0 > > > INFO (Carpet): OpenMP is enabled > > > INFO (Carpet): This process contains 1 threads, this is thread 0 > > > INFO (Carpet): There are 1 threads in total > > > INFO (Carpet): There are 1 threads per process > > > INFO (Carpet): This process runs on host robert-desktop, pid=17940 > > > INFO (Carpet): This process runs on 8 cores: 0-7 > > > INFO (Carpet): Thread 0 runs on 8 cores: 0-7 > > > INFO (Carpet): This simulation is running in 3 dimensions > > > > > _______________________________________________ > > > Users mailing list > > > [email protected] > > > http://cactuscode.org/mailman/listinfo/users > > > > Hi Robert, > > > > Can you post your machine definition file? This is the file that was > > created when you ran "sim setup". As Roland said, simfactory sets > > OMP_NUM_THREADS itself, so whatever you set in the shell in which you > > invoke simfactory will be ignored. Assuming you want a single process with > > 4 threads, you should use > > > > --procs 4 --num-threads 4 > > > > to the submission command line. This means "run on 4 cores in total, and > > use 4 threads per process". Yes, the terminology is strange. > > > > The defaults for these are stored in your machine definition file. I don't > > think there is any attempt made to default to using all the threads, but I > > might be wrong. > > > > -- > > Ian Hinder > > http://members.aei.mpg.de/ianhin > > > > > > > > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://cactuscode.org/mailman/listinfo/users > > -- > Ian Hinder > http://members.aei.mpg.de/ianhin > >
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
