RAM, runtime and credits

log in

Advanced search

Message boards : Questions/Problems/Bugs : RAM, runtime and credits

Author Message
Profile DoctorNow
Avatar
Send message
Joined: 6 Sep 09
Posts: 7
Credit: 500,736
RAC: 77
Message 1814 - Posted: 12 Dec 2017, 12:57:35 UTC
Last modified: 12 Dec 2017, 12:59:09 UTC

Hello!

Since quite some days all 14e-tasks I get do need more RAM than stated in the settings, some almost need 700 MB per task! This gave me a bit of trouble on one of my hosts (with an AMD FX 8320) in the last two days since another program also had heavy RAM usage and my 16 GB memory was almost full, resulting in an endless harddisk access storm and a slowed down system...
I suggest you update the requirements for this if it's going to go permanently over 500 MB per task!
Also, since I crunched all three types of WUs in the last time and observed how they were doing I have a question about it:
Why are credits given so inconsequently?
14e runtimes can vary from around 6000 to 10000 secs (currently), but give only 36 credits (regardless of runtime).
15e runtimes can vary from around 4000 to 6000 secs and give 44 credits.
16e runtimes can vary from around 5000 to 7000 secs and give 130 credits.
These runtimes are taken from my two hosts (AMD FX 8350 and AMD FX 8320). It's strange to me that the 8350, which is faster than the 8320, sometimes needs longer to complete a task than the 8320, although I did simultaneously crunched only one of the apps.
Given the above mentioned varied runtimes it surely would more benefit the users when CreditNew would come to use here than this fixed credit system, especially on 14e you get way too less credits on long tasks!
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Profile Carlos Pinho [TSBTs Pirate]
Volunteer moderator
Send message
Joined: 26 Sep 09
Posts: 163
Credit: 7,748,481
RAC: 756
Message 1815 - Posted: 12 Dec 2017, 17:33:47 UTC
Last modified: 12 Dec 2017, 17:33:58 UTC

The only thing we can do is change the specs at NFS@Home preferences which I've already notified the admin to do so.

We won't change the credit system since it is related to the difficulty of the number you're sieving.

Profile DoctorNow
Avatar
Send message
Joined: 6 Sep 09
Posts: 7
Credit: 500,736
RAC: 77
Message 1818 - Posted: 13 Dec 2017, 6:04:23 UTC - in response to Message 1815.

We won't change the credit system since it is related to the difficulty of the number you're sieving.

Well, this is not really logical to me.
How do you define difficulty?
If a 14e task needs twice as longer as an 16e the processor had to calculate more, so that was rather difficult than - but due to the fixed credits it gets punished the longer a tasks needs...
On a side note, I just have 14e tasks which need almost 900 MB RAM (!) and are "only" at 28% with 1h 20 min. Talk about difficulty here...
____________
Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Profile wreck2002
Send message
Joined: 5 Sep 09
Posts: 16
Credit: 26,898
RAC: 0
Message 1819 - Posted: 13 Dec 2017, 14:22:09 UTC - in response to Message 1818.

14e
C231_134_79 snfs 257 lbp 32 20-400 M
680.05 MB
-c 16000 -f 104976000
2h 42min


15e
F1327 snfs 276 lpb 32 50-500 M
552.37 MB
-c 4000 -f 109520000
1h 6min


It ' s likely that C231_134_79 should use -c 8000 but not -c 16000,
that is why it takes 2 hours but not 1 hour.

In principle, F1327 should use 16e, C231_134_79 should use 15e.
NFS@Home ' s main purpose is focus on Cunningham numbers, (a^n + 1, a^n - 1).
16e is full, so F1327 use 15e.
14e is empty, so C231_134_79 use 14e.

Message boards : Questions/Problems/Bugs : RAM, runtime and credits


Home | My Account | Message Boards