Message boards : Number crunching : problems since ACEMD 2.10
Author | Message |
---|---|
I have been running SETi and using GPUGRID as my backup project for quite some time. Ed, You may need to add this line to your cc_config.xml file: This line was already in cc_config as implied by: I have been running 2 WUs (one each) on my 2 nvidia 1070s but thanks for the thought | |
ID: 54338 | Rating: 0 | rate: / Reply Quote | |
Without knowing how Rosetta works, it's hard to say. But if turning it off gets both GPUs to run, then you already have your answer. It might be how much memory each work unit is using. Maybe they require a large amount of CPU cycles above what they say they use.(seen this in several projects where they say 1 thread but end up using 2-3 per work unit) Maybe it's how much is being written to the Hard drive each time. There could be a number of reasons. One method would be to start with only 1 work unit of Rosetta running and increase by 1 each time until the second GPU drops off. Then go down by 1 to keep both GPUs running. | |
ID: 54339 | Rating: 0 | rate: / Reply Quote | |
how much memory is actually being used on the system while it's running? | |
ID: 54340 | Rating: 0 | rate: / Reply Quote | |
Since the introduction of ACEMD 2.10 I am only running 1 WU (on GPU 0) nothing on GPU 1 and 3 WUs "in the wings". I see that you have set your preferences to leave enough CPU threads unused, and your system has as much as 32 GB RAM. Try for a while to add this "app_config.xml" on your C:\ProgramData\BOINC\projects\www.gpugrid.net directory and restart. <app_config> ACEMD3 still will use two full CPU threads through wrapper, but BOINC Manager will "think" it needs only one CPU thread for two concurrent GPU tasks... Another more exotic remedy to try: If your monitor has two inputs, you can try to connect each graphics card to one of them (one to DVI input and the other to HDMI input, for example), for both cards to be headed. | |
ID: 54341 | Rating: 0 | rate: / Reply Quote | |
I have tried running with just 1 rosetta WU and BOINC will only run 1 GPUGRID WU. | |
ID: 54342 | Rating: 0 | rate: / Reply Quote | |
Almost! | |
ID: 54343 | Rating: 0 | rate: / Reply Quote | |
Time for some other kind user with experience on Windows multiGPU systems. | |
ID: 54347 | Rating: 0 | rate: / Reply Quote | |
I found Rosetta cpu tasks tie up memory, even after you have suspended them or reduced the amount running. And that was not with leave tasks in memory setting in preferences. | |
ID: 54349 | Rating: 0 | rate: / Reply Quote | |
I found Rosetta cpu tasks tie up memory ... my experience with Rosetta, over the years, is that maximum RAM a task has ever used was about 1GB (mostly far below). Of course, the more Rosetta tasks are being processed concurrently, the more RAM they take. | |
ID: 54350 | Rating: 0 | rate: / Reply Quote | |
Rosetta takes a lot of RAM ... that's for sure ... I had 6 of them running in the 1 to 1.5 Gb range at the same time on occasion. | |
ID: 54354 | Rating: 0 | rate: / Reply Quote | |
I am running Rosettas on 9 Ubuntu machines and 1 Win7 at the moment (over 100 cores). There is no problem running them with a GPU; you just reserve a core, as usual. I switch between GPUGrid and Folding on the GPU, depending on who has work (GPUGrid at the moment). | |
ID: 54355 | Rating: 0 | rate: / Reply Quote | |
Since my last post I have done nothing but wait ... | |
ID: 54356 | Rating: 0 | rate: / Reply Quote | |
Message boards : Number crunching : problems since ACEMD 2.10