Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
k6xt:
--- Quote from: Raistmer on 11 Mar 2009, 01:16:51 pm ---This update ONLY for those who use BOINC only for SETI MB crunching. No other projects, not even AstroPulse, ONLY SETI Enhanced (MultiBeam).
In this build CPU-GPU re-scheduling is disabled (it's not needed for only SETI MB configuration).
It should increase total performance for such configs.
Again, use it ONLY if you crunch SETI MB solely.
And don't forget RULEs for opt apps updating:
1) DISABLE network access in BOINC
2) STOP BOINC
3) Copy BOINC whole data directory in another place as backup.
4) install update
5) start BOINC.
6) if all work fine - resume network access, else - stop BOINC and restore BOINC data folder from backup.
--- End quote ---
Just a suggestion it would be helpful to take the + opt AP part out of the name. This thread is confusing enough already for us non-code wizards.
Regards
Art
Leopoldo:
--- Quote from: Raistmer on 11 Mar 2009, 01:16:51 pm ---This update ONLY for those who use BOINC only for SETI MB crunching. No other projects, not even AstroPulse, ONLY SETI Enhanced (MultiBeam).
--- End quote ---
Thank You very much!
It's right my case!
[edit] Only one thing remains - don't launch GPU-part in case of VLAR workunit (do CPU, even with sharing core with already launched), so no more losses of workunits ;)
Every WU will be crunched (maybe slightly longer but no errored). Show must go on :)
[/edit]
yodi:
--- Quote from: yodi on 05 Mar 2009, 06:14:33 pm ---yodi - with already installed TightVNC - that might work fine
--- End quote ---
--- Quote from: Raistmer on 05 Mar 2009, 10:52:16 pm ---I still use remote desktop on my server host, but just don't touch local login session. That is, BOINC runs under user session logged locally and I connect to another session remotely. It works fine for me.
Think it's possible on WinXP too, you just need 2 different user accounts in this case (not sure though - didn't try this).
--- End quote ---
Hi Raistmer,
b@ck from some wired testing regarding remote desktop sessions on Windows XP. Here is the result, jFYI.
You mentioned it's possible to keep the first (local) session running on the machine when logging in as a different user via remote desktop using Vista. Tried this with XP32 and XP64 as well but unfortunately this is not possible (or I am to unexperienced to manage it), when logging in as a different user via remote desktop, the first (local) session will be terminated and I ran in the same issues (CUDA device not detected).
The describes issues seams to be related to CUDA device detection in general (rpd is using it's own video driver). Starting BOINC after logging in via remote desktop will show a no CUDA device found message within the BOINC manager.
Here is a workaround to get and keep crunching running (more or less):
1. Stop BOINC.
1.1. In case no service installation done before - uninstall BOINC and install it in protected mode (as a service).
2. Install modified V10 apps.
3. Overwrite the libfftw3f-3-1-1a_upx.dll, cufft.dll and cudart.dll with those from V8 apps. (Otherwise you'll see the same behavior mentioned earlier with the V10 stock apps: BOINC will never detect the CUDA device when logging in later via remote desktop... So the modified apps will flush all cached WUs with computation errors as it will not fall back to CPU processing.)
4. Set the BOINC service startup type to automatic (to have it running before any login).
4.1. Same for the terminal service, if not done before (this enables a remote desktop login without logging in a user locally).
5. Reboot the computer.
What will happen now is the following. The computer starts, our BOINC service as well. No user is logged in via remote desktop and BOINC will detect the CUDA device, starts computation, everything is fine.
Option 1: You login directly on the machine, nothing will change, BOINC is up and running.
Option 2: You're using remote desktop to login. As BOINC is already running, it detected the CUDA device before this login. Once you logged in via remote desktop the machine will be more than busy with the WU calculated using our CUDA device at this moment (in my case the CPU or GPU fan is more than noticeable). It will continue calculating up to 100%, throw a computation error BUT crunches all following CUDA WUs without any error, even if the rpd video driver is in use at this time.
Maybe this information is some kind of interesting. :)
Cheers,
yodi
Richard Haselgrove:
Presumably this will be different on a server-class OS, where a second user can log in using Remote Desktop without terminating any existing user's sessions.
SoNic:
Personally I am using UltraVNC to remote connect to another PC. It doesn't log off the user, it is more secure and... it works even on Vista x64.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version