Welcome to MilkyWay@home

Setting not respected - Frequency (in Hz) that should try to complete individual work chunks

Message boards : Number crunching : Setting not respected - Frequency (in Hz) that should try to complete individual work chunks
Message board moderation

To post messages, you must log in.

AuthorMessage
zablociak

Send message
Joined: 2 Sep 11
Posts: 6
Credit: 571,286,756
RAC: 0
Message 61720 - Posted: 16 May 2014, 14:09:11 UTC

Hi guys!

I'm running "Modified Fit" on my AMD HD7970 GPU with app_config.xml (only in order to run 2 tasks in parallel, no CPU tasks) and I've got a separate venue for this machine (as I run also a few CPU-only machines).
The problem is that when I set a target frequency for individual work chunks (let's say "40" instead of default "60"), this setting is not respected and all WUs are being sent with 'Using a target frequency of 60.0' all the time.

So, 2 questions:
- does it make sense to change the default value at all?
- is it possible to add <cmdline>--gpu-target-frequency 40</cmdline> into app_config.xml?

Regards
Luke
ID: 61720 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Arivald Ha'gel

Send message
Joined: 30 Apr 14
Posts: 67
Credit: 160,674,488
RAC: 0
Message 61724 - Posted: 18 May 2014, 12:46:33 UTC

Works for me:
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=745376351
for MilkyWay@Home tasks.
Does not work for Separation (Modified Fit):
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=745154872

So probably just missing statement that it only works for MilkyWay@Home, or indeed a problem in coding :)
ID: 61724 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Setting not respected - Frequency (in Hz) that should try to complete individual work chunks

©2024 Astroinformatics Group