Welcome to MilkyWay@home

Posts by PeteS

1) Message boards : Number crunching : Marked as Invalid? (Part 2) (Message 38182)
Posted 6 Apr 2010 by PeteS
Right, I already posted an alert over at Collatz so that Slicker is aware of the incoming rush of MW folks looking for a productive home pending Travis issuing the appropriate 'undo' command to the validator 'fix' which has been implemented here.

For the time being my 5830 is going over to Collatz as I cannot seem to get above a 66% valid rate.

I can do more over there at the moment.

Don't forget DNETC@Home which also works on ATI and nVidia.
2) Message boards : Number crunching : Marked as Invalid? (Part 2) (Message 38181)
Posted 6 Apr 2010 by PeteS

Some get credit and some don't for the same WU????
3) Message boards : News : lowering purge time (Message 36165)
Posted 31 Jan 2010 by PeteS
Does this affect sending results back? Before Boinc Mgr processed pretty much my whole queue of MW Wu's, but now on all comps it seems to send&report every wu immediately.

Not a big problem for me, but if this is the same for all users this should create a lot of network traffic and I/O on server?
4) Message boards : Number crunching : iPhone (Message 36161)
Posted 30 Jan 2010 by PeteS
UltraVNC supports Vista and Win7. Using & works great. You could try installing ultravnc on vista comp and then try viewing with tightvnc or some other vnc client.
5) Message boards : Number crunching : Down for maintenance? (Message 35733)
Posted 17 Jan 2010 by PeteS
Weekend: Results ready to send 0
6) Message boards : Number crunching : ATI GPUs? (Message 34814)
Posted 24 Dec 2009 by PeteS
I have 2 3870X2's so 4 gpu cores, however boinc and gpuz shows that only 2 gpus are being used, how can I sort this out?

Are you running in SLI mode? Should be no.

Have you extended your desktop to the other card? Required.

Do you have a dummy plug in GPU number 2? Required on Vista and Win7.

No dummy needed if destktop is extended. Tested & Works on Win7.
7) Message boards : Application Code Discussion : GPU app teaser (Message 34212)
Posted 4 Dec 2009 by PeteS
Seems like 0.20b is at fault here, been running 0.19f for a while without problems...
8) Message boards : Number crunching : Problem with tiny cache in MW (Message 33991)
Posted 30 Nov 2009 by PeteS
I understand that fast turnaround times are important (not even going to the fact that slow Quad CPU's take ages to return the wu's).

BUT defining the amount of WUs to send to GPUs by the amount of CPU cores is just flawed by nature. I have f.ex. two GPU crunching boxes with AMD A64 one core CPUs with powerful GPUs, these have some five minute of MW work cache, that is just ridiculous. Compare to GPUGrid with two WU's / GPU and these WU's run some 10 hours. They also depend on results returned to generate new, yes?

edit, read only with time:) Just read all the fighting below. I think this project is already only good for a specific group of people. To crunch here means you need to babysit computers, work hard to get a working OS/Driver/ATI app configuration just to get the app running decently. If you want to attract masses this should work as reliably as WCG f.ex. where you can keep Boinc Mgr in simple mode. The app's never crash, no manual intervention needed.

I find other needs more important when selecting my driver and OS, I want the latest stuff. Not legacy old versions just to be able to crunch one project. Most of us pay high electricity bills and get new components so that we can do this kind of charity work called Distributed Computing. But we should be provided with good support, stable applications and so on for our free help... /end
9) Message boards : Application Code Discussion : GPU app teaser (Message 33989)
Posted 30 Nov 2009 by PeteS
10) Message boards : Application Code Discussion : GPU app teaser (Message 33988)
Posted 30 Nov 2009 by PeteS
Will there be any improved ATI GPU applications planned for near future? I'd like to contribute by running these, but with most of my computers I can't get the app to run without occasional VPU-Recoveries. As you probably know this causes the ATI App to hang up, using 100% of CPU and the time counter on the task/wu increases but progress is halted -> Total waste of nerves, electricity, time etc.

CP/Gipsel you did the app also for Collatz. With Collatz all my computers run flawlessy (one up over month in a row without a single problem) but MW is very picky on OS/Driver combinations and for some like me it does simply not work reliably for longer periods of time. I HATE to keep watching my computers all the time and restart BOINC Mgr with jammed ATI MW tasks and for this reason I am not crunching MW.

Any change of getting the reliability of the Collatz App over to MW? Any change of improving the code to prevent these driver errors? Any chance of somehow automatically notice jammed tasks and kill these?
11) Message boards : Number crunching : new hard drive installed (Message 33666)
Posted 24 Nov 2009 by PeteS
Congrats to the new Dr. and great to see some positive movement in MW! I'm back to MW now after quite a long break!

Hope you still have the following on todo-list:
- GPU only side or very much longer wu's
- increase the limit of wu's from 6/cpu to xxx/gpu
- These fitness calculations do not reveal what the milky looks like, do we have graphical rendered presentations? ;) I wish to see my contribution to science in more detail..
- Having working GPU scheduling in Boinc Manager and an updated ATI-client that works on all OS/driver combinations without VPU errors!
- Having active admins / project personnel on forums surely help in attracting volunteers and makes us feel appreciated. Someone is actually listening!

I'm in this all for the science! Have to also wonder about this credit issue, as long as it's the same for all participants it should not matter what the amounts are. Constant adjustments just make people angry. Like many have stated, credits are just numbers, they are not worth anything! :)
12) Message boards : Number crunching : windows 7 (64bit version) ? (Message 32302)
Posted 11 Oct 2009 by PeteS
I mean that Win7 is based on Vista, and when 8.12 was released they did not mention Win7 in driver name. So you can install 8.12 driver for Vista :)

13) Message boards : Number crunching : windows 7 (64bit version) ? (Message 32300)
Posted 11 Oct 2009 by PeteS
sure it works. best to stick with vista 8.12 drivers, all others will just cause problems with mw! 9.5 was ok before 0.20 version, after that I have only working systems with 8.12 even under win7x64.
14) Message boards : Number crunching : astronomy_020.ATI_x64 problems (Message 32226)
Posted 10 Oct 2009 by PeteS
As you CP/Gipsel wrote both MW and Collatz ATI-apps, is it possible to update MW-app to work as well as Collatz-app? With Collatz I am running with Cat9.9 and almost never get display driver resets (jammed up tasks for long times), but with MW this happens hourly. CAT9.5 was working better.

So far I have set MW to NNT on all computers.

I have also tried to find a good solution to automatically kill the jammed up ATI-app but no good solution found yet. Anyone got this handled in a smart way?
15) Message boards : Number crunching : Problem with tiny cache in MW (Message 31699)
Posted 29 Sep 2009 by PeteS
I totally agree on making this CAL/CUDA only. Then you can rely on fast enough response times and set due date quite agressively + have a longer wu queue. There are a lot of CPU only projects where CPU's are needed, here using a CPU seems like quite a waste when exactly the same can be achieved with much faster GPU's.

Ice, if you really think about it, that is a really bad excuse for keeping CPU apps around <a lot of examples here>.

I am also thinking of moving totally to Collatz since things really progress slowly here and the project is often down. I just wish projects like WCG had GPU apps, since I have never problems there.

I have also tried setting primary+secondary projects, but with no success.
- Promise to set up GPU project ->never happened
- Promise to set higher queues ->never happened
- Promise to make much longer wu's ->never happened
and the list goes on. I'm a real fan of sci-fi and wish to help human kind progress more rapidly, and that's why I pay big electricity bills and have many computers counting BOINC projects.
16) Message boards : Number crunching : Problem ATI v0.2 and Win7? (Message 30860)
Posted 14 Sep 2009 by PeteS
I also could not get 0.20 running, and none of the normal mistakes were made.. finally I could not return succesfully to 0.19 before copying the entire folder from another machine.

ATI9.5, 4850, win7x64, 6.6.36. Had all the files, removed 6.10.x specific lines in app_info, had the renamed dll's in system32.. just could not get it working. Any ideas from the failed tasks?
Incorrect function. (0x1) - exit code 1 (0x1)
Running Milkyway@home ATI GPU application version 0.19e by Gipsel
allowing 2 concurrent WUs per GPU
CPU: AMD Athlon(tm) 64 Processor 3200+ (1 cores/threads) 2.30077 GHz (425ms)

CAL Runtime: 1.4.283
Found 1 CAL device

Device 0: ATI Radeon HD 4800 (RV770) 1024 MB local RAM (remote 319 MB cached + 319 MB uncached)
GPU core clock: 735 MHz, memory clock: 1000 MHz
800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

0 WUs already running on GPU 0
Starting WU on GPU 0

main integral, 320 iterations
predicted runtime per iteration is 195 ms (33.3333 ms are allowed), dividing each iteration in 6 parts
borders of the domains at 0 266 533 800 1066 1333 1600
0 Kernel Execution : Failed to create Program

17) Message boards : Number crunching : deja vu! (Message 29087)
Posted 9 Aug 2009 by PeteS
Results ready to send 0
Results in progress 65,239
Workunits waiting for validation 44
Workunits waiting for assimilation 2
Workunits waiting for deletion 210
Results waiting for deletion 409
Transitioner backlog (hours) 0

It's just hard to understand WHY oh why not start the separate GPU project with ATI now, and use WU's which take many hours to process (with correct checkpointing to allow resume). And also wondering how and why the project decided that the single precision part will be discarded, after CP said the ATI version is very precise in it's calculation, lot of wasted work there.

Just start with Crunch3r's modified 6.6.20 APP and do server side changes, and we can kiss goodbye to so many problems..

//Message from an amateur ends, who has done a lot of work (Virtual machines even) to get CPU+CUDA+CAL to work on same computer.
18) Message boards : Number crunching : GPU Card Problem (Message 27652)
Posted 13 Jul 2009 by PeteS
I also have problems with my 3850 oc card. I have tried numerous settings, some help (not solve) but then the GPU utlization is really low. I now have "Computing allowed when computer is in use" set to disabled, but still sometimes get VPU recoveries and the ATI 0.19f App is in a neverending loop taking 100% of the CPU, until at some point I notice it and restart boinc. I have no probs with my 4850 and 4870 cards, also Furmark runs nicely on the card so I suspect the card is working fine "hardware wise".

I still feel you have a slightly different problem, as your WU's error out immediately. Do you get a VPU Recovery? Have you overclocked? Have you tested that you get no artifacts running Furmark? How are the temperatures? Have you read the readme, all settings ok and files installed properly?
19) Message boards : Number crunching : 4890 support (Message 27119)
Posted 5 Jul 2009 by PeteS
I have seen some discussion here and there, but thought it would be best to make a new thread about it (not to mess other threads and get enough attention)

- Does MW work on 4890?
- I remember Poorboy having one, but still seen him asking how to get it working, correct?

I am in the process of ordering a new computer, and hesitating whether to get nVidia 285 (GPUGrid&SETI) or ATI 4890(MW). This comp will be used also for games, where both of these perform roughly equally.
20) Message boards : Number crunching : Compute Errors (Message 26680)
Posted 29 Jun 2009 by PeteS
Can you people using 3850 tell what settings you are using in app_info.xml? I have tried many different settings, but still get VPU Recovery events..

I am running on Win7 64bit, ATI 0.19f and BOINC 6.6.36

Everything is fine and the WU's are processed at peak efficiency IF I don't do anything on the computer. But if it is used normally (watch videos, browse web with Firefox etc) then I constantly get blank screen+VPU recovery+jammed WU that I have to either kill with task manager or restart BOINC. I don't seem to have this problem on my 48xx series cards only the 3850.

I get somewhat better functionality (still problems but less) with f60 w1.7 n1, but then GPU utilization is only 50-60%.

Next 20

©2023 Astroinformatics Group