Welcome to MilkyWay@home

fpops and memory bound estimation

Message boards : Application Code Discussion : fpops and memory bound estimation
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Travis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
Message 6640 - Posted: 24 Nov 2008, 23:01:03 UTC

Anyone have any good methods or suggestions for getting accurate fpop and memory bound estimations for the milkyway app?
ID: 6640 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile JLDun
Avatar

Send message
Joined: 17 Nov 07
Posts: 77
Credit: 117,183
RAC: 0
Message 7497 - Posted: 6 Dec 2008, 4:56:39 UTC - in response to Message 6640.  

Accurate fpop ... estimations

Don't know how much this helps, but my laptop is running the 0.7 application in 9466.515625 seconds (~3:0x) with a DCF of 0.196707; I don't know about others but the estimate can be reduced to around 1/5th in my case.
(What's the DCF for the project right now?)
ID: 7497 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile banditwolf
Avatar

Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 524,164
RAC: 0
Message 7784 - Posted: 16 Dec 2008, 4:26:50 UTC - in response to Message 6640.  

memory bound estimations for the milkyway app?


Not sure if this is what you are after, the final 5 seconds of running the memory usage jumps up to 150-160k.
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.
ID: 7784 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Travis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist

Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0
Message 8584 - Posted: 18 Jan 2009, 15:37:53 UTC - in response to Message 7784.  

memory bound estimations for the milkyway app?


Not sure if this is what you are after, the final 5 seconds of running the memory usage jumps up to 150-160k.


I think this was caused by the memory leak in the likelihood calculation. This should be fixed in versions 0.8 and later.
ID: 8584 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Application Code Discussion : fpops and memory bound estimation

©2024 Astroinformatics Group