[Users] cactus performance

Jose Fiestas Iquira jafiestas at lbl.gov
Wed Mar 28 22:31:47 CDT 2012


Hello,
Regarding performance. I am willing to run McLachlan shortly using CrayPat
and I am setting the simulation time here in par/qc0-mclachlan.par, like
this:

Cactus::terminate       = "time"
Cactus::cctk_final_time = .1

usually this time was 100.

Am I missing something else in setting the time for a short simulation? I
could not find it in the documentation.

Thanks,
Jose

On Mon, Mar 26, 2012 at 10:44 PM, Jose Fiestas Iquira <jafiestas at lbl.gov>wrote:

> Dear Uschi,
>
> Thanks. I am right now trying CrayPat. I learned about it some days ago
> and tried my own N-cody code with CrayPat. I am using now the McLachlan
> Cactus thorn for my applications.
>
> I am just not sure about the way to compile the code before running
> CrayPat. I was using simfactory for compilation and now I am using gmake
> directly. Since compilation takes some time, I am waiting for it to finish.
> Let see if it works.
>
> The reason I am interested in Flops is because I want to know if my Cactus
> application will scale together with my own N-body runs in large machines
> and reach Petascale.
>
> Btw, did you try CrayPat with Cactus? You use gmake for compiling?
>
> Best,
> Jose
>
>
> On Mon, Mar 26, 2012 at 10:20 PM, Ursula Gamma <uschigamma at yahoo.com>wrote:
>
>> Dear Jose,
>>
>> I think the best is you use a performance checking tool coming with your
>> computer. For example  PAPI or
>> CrayPat (on your lbl machine:
>> http://www.nersc.gov/users/software/debugging-and-profiling/craypat/).
>> You need to access hardware counters for getting the flops; this is not a
>> software feature. Counting flops is so last century, though, and nobody
>> talks about this these days. I am usually just interested in getting the
>> shortest possible walltime for a given problem I want to solve with my
>> Uschi evolution code in the Cactus framework.
>>
>> Uschi
>>
>> ----------------
>> Uschi T. Gamma
>> Assistant to the SC, TAPIR, Caltech
>>
>>   ------------------------------
>> *From:* Jose Fiestas Iquira <jafiestas at lbl.gov>
>> *To:* Ian Hinder <ian.hinder at aei.mpg.de>; users at einsteintoolkit.org
>> *Sent:* Monday, March 26, 2012 8:58 PM
>>
>> *Subject:* Re: [Users] cactus performance
>>
>> Hello,
>>
>> Thanks for the information. I had a look at the benchmarks and profiling
>> links on the Cactus website, and would like to find out the way to
>> calculate Flops performed by a Cactus application. Are they some numbers
>> published? In one of the papers you sent to me I found timings of McLachlan
>> (which is my application), but I could not find Flops per simulation.
>>
>> It seems to me I could be able to run my application using .par-files
>> prepared for benchmarking? Please correct me if I am wrong.
>>
>> My goal is to have an idea of the Flops expected by McLachlan runs on
>> larger machines (few thousands or cores).
>>
>> Thanks,
>> Jose
>>
>>
>> 2012/3/21 Frank Loeffler <knarf at cct.lsu.edu>
>>
>> On Wed, Mar 21, 2012 at 01:15:05PM +0100, Ian Hinder wrote:
>> > Frank, do you know what the following links have changed into?
>> >
>> > http://www.cct.lsu.edu/xirel/
>> > http://www.cct.lsu.edu/CCT-TR/CCT-TR-2008-5
>>
>> Good question, I made an inquiry.
>>
>> Frank
>>
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.10 (GNU/Linux)
>>
>> iQIcBAEBCAAGBQJPaelqAAoJEOkzpip+I59kRocP/RZl0R9MEiM5r/HfB+JZkwXs
>> cA3eXKJeqiHtzsmqqruH/AI7zcR8zpq+BsrWHmtJQecqp28JqoV1+G7V8Z7cB/os
>> 4pI0KFQQ6npRmnWytBSLrextanvLooqFgEB62S78MsyucTgzJwVX1AOkDuYQpHPO
>> 3V6LQO7Jmcj5m2OoVr74mI/IFDermdwE/84dyjbz5tRrKPTug7qjfjFrfKT9yysK
>> unA6oKl9zEdm1KZvDKzPTPh6hCcI1NNC+uRoNMnBu3XQprgNvZ/N8iDomrodCjhO
>> iqKy5DVBhZVJhh//dWYuTzRu/l0MPMv4WML0OJmeLgbYerW2m+17lwAgumtccqwk
>> OOuGTUqVfF9VuHJQ17jZ4jVyAjl9pIHENJCDZjmwNBDONinUC3Igjza3YlSHOCzU
>> 1QUU1eomrSvA1oKThfaTKj+vpd+IjncucmQAtVW5rsiMjKQoOMajyR13kMJ6e8Y6
>> uooQr8wXJBJqiN48QBS3XvGTixvAeXmT+bQtBpocyr6vN4vEPBfwWymTn2sfd/XA
>> vd/7Rps/IH9x3bbkk3eqCHiHrxvqPBfNdm/KbI20SZUT88XbFawuL7l1X3UgKCLv
>> fjRNPFxtHQsz3CYk/z6YllKgf6xp34XYshtGnl6LE9lS2If8GOXIMR+MdgGJndre
>> FXx7kXx6Oj4TLYsqOE0f
>> =vnYk
>> -----END PGP SIGNATURE-----
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at einsteintoolkit.org
>> http://lists.einsteintoolkit.org/mailman/listinfo/users
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.einsteintoolkit.org/pipermail/users/attachments/20120328/b28129f8/attachment.html 


More information about the Users mailing list