Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 63
|
![]() |
Author |
|
sgoll
Advanced Cruncher Joined: Oct 24, 2006 Post Count: 87 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Well, I'm a bit late on this thread, but the topic sounds interesting. I have some crunchers, but 2 of them are equipped with exactly 256 MB of memory. I can remember that when these 2 were running DSFL task all results were invalid. My other systems are fine. I stopped DSFL after getting gold because it is a bit annoying to waste cpu time. All the other projects on these 2 systems are fine ... so I'm sure it is not overheating or such like.
----------------------------------------Yes, I agree with the "DSFL seems to like more memory" idea. The systems i question are running linux, client version is 6.10.58. I have no idea what will be enough memory for DSFL, but 512 MB may be enough. 256 seems to be too little. If one wants me to reproduce the errors ... let me know. But until then I think raising the requirements for DSFL would be a very god idea because this would prevent me from wasting cpu time for this project again. Stephan ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi Stephan,
normally a single DSFL-task needs not more than 64 MB, my own experience under several different windows-platforms. But keep in mind that every driver, every other program you run and even the operating system itself needs memory. So if you have 256MB of free RAM if your system is up and running, you are on a safe side. The requirement for RAM is the amount of free RAM a task needs for proper processing, independent from the size of your installed amount of RAM-"hardware". 256 MB in this case could be not enough, depending of the things i told above. And for sure, linux maybe the better choice of your running os, if you have a very low amount of RAM, often it's simply doing a little bit better work if it comes to the point of insufficient RAM. So check your amount of free RAM under typical running conditions, I am very sure there is far far less availabele then 256 MB. There is no need in changing the requirements here in my opinion. If low RAM is the problem of your invalid or errored results then you have 3 choices. Install more memory into your machine, decrease the amount of simultanously running programms/drivers or you have to switch to another project. As far as I know, the only project needing explicit less RAM is HCMD Phase 2 here, don't know if it is still running. You can also try other projects except CCW, CEP 2 and DDD 2, these 3 projects needing much more than 250 MB. Hope this helps? Cheers Andi |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello, somemore...
I have sucessfully run DFSL wu's on e566 intel machines with ONLY 256 RAM...BUT they do take time.. in the range of 65-85 hrs. I have since restricted these machines to Faah (45-54hrs)and Hpf(similar times),and CMD. HOWEVER, just an FYI. I was stumbling around the internet and found a small pgm that FORCES the OpSys to/towards selected programs when the OpSys wanders off to do (WCG) useless processing. Here's the URL: http://www.raymond.cc/blog/archives/2007/08/2...y-when-cpu-usage-is-high/ I have realized 15-120%(<-e566 machines) increases in thru-put for wu's using this. Have seen my "Points/day" increase from 30da average of 10,000-10,500 to 12,000-12,500 with all (10) machines running fixed projects. It works on all the Windows opsys's (didn't see a linux version)and have it installed/running on ALL my single and duo core. machines. Just a heads up.....Keep on crunchin' |
||
|
|
![]() |