Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Completed Research Forum: Say No to Schistosoma Forum Thread: SN2S tasks become suddenly much heavier on RAM - please update minimum requirements |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 11
|
Author |
|
Randzo
Senior Cruncher Slovakia Joined: Jan 10, 2008 Post Count: 339 Status: Offline Project Badges: |
Hello,
I'm now running 8 SN2S tasks on my VMs concurrently. RAM usage used to be up to 800 MiBs (Linux OS takes ~ 220 MiBs), but tasks downloaded today consume up to 3,5 GiB. I had only 2 GiBs allocated for the VM I thought initially that it is some memory leak as far as it allocated all RAM and swap in few moments. After I allocated more memory to the OS it is running OK. I would like you just to update system requirements https://secure.worldcommunitygrid.org/help/viewTopic.do?shortName=minimumreq there is an info that SN2S requires 250 MB, which is not true according to my observation. Thank you. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's several topics 'already' on that, which FTM seems limited to certain targets.
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There's several topics 'already' on that, which FTM seems limited to certain targets. That should still be noted in system requirements. |
||
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: |
We've increased the system memory usage for SN2S to reflect a few of the larger targets that use up more memory than the others. We had decreased it to 100MB as most targets for VINA were smaller than that. The target is like a box, the bigger the box for the search, the more memory and they can get large quick.
Thanks, -Uplinger |
||
|
Randzo
Senior Cruncher Slovakia Joined: Jan 10, 2008 Post Count: 339 Status: Offline Project Badges: |
Thank you very much Uplinger for changing the requirements.
I'm completely OK with larger memory consumption, but it should be stated as far as I had no idea at the beginning of TS what could be going on. Keep on with great work! |
||
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges: |
The target is like a box, the bigger the box for the search, the more memory and they can get large quick. Do you have plans to offer these bigger SN2S tasks to the community? Maybe optional? I think a lot of hardware resources out there are capable for those tasks. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
When I wrote in my first reply that there were several topics already there, before Randzo posted, that was to indicate that these 'bigger' memory using tasks [specifically batches that have the 4AOD and 4AOE monikers) ARE in circulation, so why asking to offer them to the community?
In general, whatever uplinger meant to convey and Randzo thanked for, the OP noted the spec was 250MB -AND- it still is, but 4AOD and 4AOE can run up to 578MB RAM using models, on top there being VM [that's the biggest my BOINCTasks logged]. The only concern I have is that these 2 specific targets go to Android devices, but, I'm entirely unclear if SN2S at all is going to Android devices. The same System Req. page says they are released, but there was never a launch announcement I can recollect, except for a beta and never seen Android comments of problems with SN2S in production. So are they? For good order these big ones come and go. Since there is no method of dynamic limitation within a science at this time, the choice seems to me to either allow these to go to all devices that meet the 250MB requirement [formerly 100MB], or up the limit further, which will cut out a bunch of volunteers. Then there's of course the comments of members aborting them because 8 biggies [I've had them going simultaneous on a 8GB device], on a 4GB system is taxing and users notice. As BOINC is supposed to work, if memory limits were set default, left default(!), some tasks would be paused automatically when the user needs the computer. If the user then chooses to set "compute while in use and allow BOINC 99% memory during use" [yes read that], then that is self-programmed trouble. The person to look hard at is the one seen in the mirror. Extraordinary to me is, that systems [PC's] are not fitted with 1GB per thread i.e a duo having 2GB, a quad 4GB, an octo 8GB etc. Model sizes vary and they've been doing that for a very long time. If you don't have that, don't mess with the BOINC defaults and expect not to be bothered by crunching. That was for the general readership. |
||
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4848 Status: Offline Project Badges: |
The only concern I have is that these 2 specific targets go to Android devices, but, I'm entirely unclear if SN2S at all is going to Android devices. The same System Req. page says they are released, but there was never a launch announcement I can recollect, except for a beta and never seen Android comments of problems with SN2S in production. So are they? I have not been able to download any SN2S WUs to my adroid devices. |
||
|
mwgiii
Advanced Cruncher United States Joined: Aug 17, 2006 Post Count: 131 Status: Offline Project Badges: |
I'm entirely unclear if SN2S at all is going to Android devices. The same System Req. page says they are released, but there was never a launch announcement I can recollect, except for a beta and never seen Android comments of problems with SN2S in production. So are they? I finally got around to trying BOINC on my 1st gen Kindle a little over a week ago. SN2S is the only project checked along with "If there is no work available for the project(s) I have selected above, please send me work from another project." I have yet to see a SN2S wu. I do receive a steady supply for FAH though. |
||
|
Thargor
Veteran Cruncher UK Joined: Feb 3, 2012 Post Count: 1291 Status: Offline Project Badges: |
Not sure if I'm not yet seeing the newer-style tasks, but my cluster of five VMs (each "server" is a four-core debian-build limited to 1.5GHz per core, and 768MB of RAM) appear to be having no major issues so far.
----------------------------------------I've seen an occasional spike into swap-memory, which isn't overly ideal, but that was occasionally happening before this requirement-change. EDIT: have now seen some of the newer work-units on my little VM-cluster, and the fact that one WU required 450MB of RAM means I've had to disable SN2S from running on those five VMs - they only have 768MB RAM, so I have to be very careful about memory usage on them. FA@H only uses 80-100MB per WU, currently, which means I'm not dropping straight into swap. [Edit 1 times, last edit by Thargor at Sep 6, 2013 10:58:21 AM] |
||
|
|