| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Retired Forums
Forum: UD Windows Agent Support [Read Only]
Thread: 200 MB VM size normal on Windows XP? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have the grid running on a Windows XP 2 Ghz Pentium IV machine with 512 MB memory. I just found out that the grid is having a VM size of 200 MB(!) of which 25 MB is in physical memory. The total amount of allocated memory in the system is well over the available amount of physical memory. Does the grid just take as much as it can use, or is there something wrong?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nah the grid (rosetta app) always takes alot of virtual memory but that aint bad. You won't notice that in system performance. I thought it had something todo with disabled features in the rosetta app. I might be totally wrong
 BTW, I think this thread belongs in another forum (Windows Agent Support) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello schreurs_roel,
The original Rosetta program was a large Fortran program with large statically allocated arrays that took up more than 500 MB (gives you an idea of why it used to take a supercomputer to run serious scientific programs). Our version of Rosetta was translated to C++ and was cut down to only contain the routines we need for this project. Because it retains the static arrays it needs about 200 MB of Virtual Memory, but the working set of memory pages is only about 25 MB, so it can run on a Windows XP system with only 128 MB of RAM. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Y'all must KISS... ya need 25-256 ram & 25-300Meg-a-disk and any ol' NET connection to compute ! now ,of course y'all need a dependable CPU - hopefully not a reject that will burn-up from COMPUTIN'!but we have learnt...and Lindows machine hasn't fried yet, but we rebuilt 2 XP-AMD-athlon machines to con't. to contribute and also BEEF'D up our memory and 'MASS-STORAGE' to handle ANYTHING [fans and Fall weather helps too!] All is well in ZEROEZ-land. regards. ps: as me about RAM drives and Thumb-drvs at NANOSecz....... |
|||
|
||||
|
Alther
Former World Community Grid Tech United States of America Joined: Sep 30, 2004 Post Count: 414 Status: Offline Project Badges: 
|
mycroft for the most part has it correct regarding the history of Rosetta and why it takes up the memory it requires.
----------------------------------------Regarding the impact to the system, there is an impact, but it's only short term. Let me explain. As stated, Rosetta allocates 200MB of virtual RAM when it starts up. As far as Windows is concerned this might as well be real RAM because Windows doesn't know that it's only going to us 25MB. Thus, Windows may very well start paging in preparatoin that the program may actually use all 200MB. If you have less than 1GB of RAM, you will likely notice this as paging adversely affects the performance of any system. However, after a while, Windows notices that Rosetta has only touched 25MB of RAM and in the course of paging will eventually permanently page out the other 175MB of RAM, making room for other other programs. Thus, after a while, Rosetta really is only actually taking up 25MB of RAM and the impact on anyone's system becomes "minimal".
Rick Alther
Former World Community Grid Developer |
||
|
|
|