Forum > GPU crunching
VBscript Fights Cuda
Maik:
Hi there!
Maybe you know me from Seti Board. Raistmer was suggesting me to join here.
Here i am ! ;) You should know my first language is German, so please be patient with me if my english looks a bit silly ^^
Ok, on work:
Maybe you know i have written a VBscript that watches Cuda-app.exe and fights with its freezing.
--- Quote from: Raistmer ---
--- Quote from: Maik ---vbscript is modified and will copy automaticly wu's which get stuck, tested -> works
now ill try to modify the script that it also will do a copy of WU's that ran to short (compute error) ...
then i'll have my full-auto-watching-wu-and-copy-it-to-stand-alone-dir-vbscript ;))
--- End quote ---
Wow, very nice !
It seems it's very useful to master VB scripting, will look in this direction, thanks for info :)
--- End quote ---
After that PM i was thinking i should report here what i have done:
# i created 2 scripts, one for normal use (cuda_log), one for users who do stand alone tests (cuda_log_test)
-> cuda_log activity:
' watching cuda-app.exe
' terminating it when cpu-usage is 0 over 60sec
' logging to file / monitoring at cmd-window all activities
-> cuda_log_test activity:
' same as cuda_log +
' counting task-runtime and monitoring / logging it
' if runtime below defined time -> copy WU to defined folder (to catch compute errors / result overflows)
' if task get freezing -> copy WU to defined folder
' (on my to-do-list -> copy of stderr)
Be carful if you use that 'automated' WU-cleaning (process-terminating). Check your host from time to time.
Some WU's are causing your grafic driver to crash. The result are a lot of failing WU's in a row (noticed that this morning at my host).
The crash announces itself with around jumping pixels everywhere. Some users posted that already ...
If you want to use the script please focus your attention to the settings. Wrong settings will make the script to fail.
I will explain them in my post.
The scripts is running fine at my host (WinXP Pro SP3).
If the script want start, maybe 'scipting host' is deactivated (via xp-AntiSpy or other tools like this)
Edit: delete files-downloads (newer one)
Extract the file where you want and where you have full access (create-file, change-file, e.g. C:\temp).
DONT double-click the *.vbs-file. Windows will use the wrong application tu run the script. Just double-click the *.cmd-file, its the starter-file for the *.vbs-files.
Example from script output:
--- Quote ---04.01.2009 01:48:11 > Process-Control for MB_6.06r380mod_CUDA.exe
04.01.2009 01:48:11 > logFile: pc_log_0_04012009.txt
04.01.2009 01:48:11 > maxLogFileSize set to: 51200 bytes
04.01.2009 01:48:11 > boinc dataDir found
04.01.2009 01:48:11 > standAlone folder found ... sub-standAlone activated
04.01.2009 01:48:11 > - running ----------------------------------------
04.01.2009 01:48:11 >
04.01.2009 01:48:14 > --- watching new WU-file: 06no08aa.9787.12342.9.8.106_0
04.01.2009 01:48:29 > ID: 3540 MB_6.06r380mod_CUDA.exe 6 %, running: 15s
...
04.01.2009 01:55:01 > ID: 3540 MB_6.06r380mod_CUDA.exe 12 %, running: 407s
04.01.2009 01:55:16 > --- watching new WU-file: 06no08aa.9787.12342.9.8.125_0
04.01.2009 01:55:31 > ID: 2020 MB_6.06r380mod_CUDA.exe 36 %, running: 15s
...
04.01.2009 02:03:32 > ID: 2020 MB_6.06r380mod_CUDA.exe 12 %, running: 496s
04.01.2009 02:03:47 > ID: 2020 MB_6.06r380mod_CUDA.exe 12 %, running: 511s
04.01.2009 02:04:02 > --- watching new WU-file: 06no08aa.9787.12342.9.8.93_1
04.01.2009 02:04:18 > ID: 2988 MB_6.06r380mod_CUDA.exe 18 %, running: 16s
04.01.2009 02:04:33 > --- watching new WU-file: 06no08aa.9787.12342.9.8.112_0
04.01.2009 02:04:33 >
04.01.2009 02:04:33 > --- debug > RunningTime: 31 --- MinRunTime: 120
04.01.2009 02:04:33 > File: 06no08aa.9787.12342.9.8.93.wu copied ...
04.01.2009 02:04:33 >
04.01.2009 02:04:33 >
04.01.2009 02:04:48 > ID: 1016 MB_6.06r380mod_CUDA.exe 4 %, running: 15s
--- End quote ---
Maik:
To change settings right-click the *.vbs-file -> context-menue comes up -> choose open with ... -> use notepad.exe
All settings are explained with comments (comments beginning with ')
Settings in cuda_log are easy to understand i think.
For cuda_log_test users, scroll a bit down, there you will find a comment
'settings only for stand alone to copy WU's
To make the script to copy files ssp must be true (ssp = true)
To set your temp-folder is sspp for ...
sspp = "D:\boinc_data\KWSN Knabench 1.43\TestWUs\Reserve\"
Here set the time in seconds that the WU should run to be not a cumpute error / result overflow
(normally WU's are canceled from set-app after 30 sec if result overflow happened)
appMinRunTime = 120
OK, nuff said ... Your turn ;)
Jason G:
Sounds like I might be able to try the App again with this, thanks Maik, Will try later today. May take a looksie what is causing these issues If I get a chance.
Maik:
-
I have a request:
If you use the script please notify me about errors (with error messages).
I cant bugfix it if i read posts like 'i have changed that and now it runs' as it happend in seti-forum.
-
Thanks
Raistmer:
@Maik - can't send PM to you - PM limit reached. I deleted some messages but still the same - maybe it's your PM limit reached not my ?
Check this, please.
Navigation
[0] Message Index
[#] Next page
Go to full version