Welcome to MilkyWay@home

Posts by Conan

41) Message boards : Number crunching : Conflict MW (ATI) & Aqua CPU (Message 29029)
Posted 8 Aug 2009 by Profile Conan
Post:
Well both Milkyway and Aqua both run in High Priority on my machines.
They still both seem to work switching when required.

The Linux machine I have left 'as is' and it runs CPU Milkyway WUs OK as well as AQUA, Climate Prediction, Docking and QMC.

The Windows machine runs Milkyway on an ATI HD4870 with AQUA, Docking and Spinhenge on the CPUs.

I modified the cc_config.xml file on the Windows machine to show 5 CPUs (I have 4) and use 6.4.7 Boinc Client with 8.12 ATI drivers on an Win XP SP3 install.
Milkyway runs 3 jobs at once as per default settings for the card.

With AQUA using up to 4 CPUs it still leaves room for Milkyway to run on the ATI GPU. Has been working a treat so far.

The High Priority appears to have begun with the last couple of batches of AQUA work units, but for me is not causing a problem.

Conan.
42) Message boards : Number crunching : BSoD with 0xF4 stop error, catalyst 8.12 (Message 28703)
Posted 1 Aug 2009 by Profile Conan
Post:
After few mins of work WinXP stops by BSoD.
GPU: HD4870, driver Catalyst 8.12.
Any suggestions what could I try to solve this problem?
GPU works OK if MW stopped.


Not sure what could be causing this as I have the same set up and am having no problems (Win XP, Catalyst 8.12 and an HD4870 graphics card).
I run AQUA, Docking and Spinhenge (projects like Rosetta, Cosmology and a few others use too much memory and stop the card from working properly) on the CPUs with Milkyway on the GPU

What else are you running at the same time as running Milkyway?
43) Message boards : Number crunching : Updating Server Daemons Tonight (Message 28172)
Posted 22 Jul 2009 by Profile Conan
Post:
Started a Genetic Search
July 21, 2009
I'm testing a genetic search right now with the new verification. Let me know how things are working. Work should be flowing now


The above is a quote from the front page

Sorry Travis but there is NO work flowing at the moment and has not been for at least 2 hours.

Running out of work, can you help please and kick the work generator in the bum.

Thanks
Conan.
44) Message boards : Number crunching : GPU RAM and RAC. (Message 28141)
Posted 21 Jul 2009 by Profile Conan
Post:
Hi all!
Does the amount of RAM on the ATI 4870 based card
affect the RAC?
Seeing as how they are sold with 512meg and 1024meg
versions,will the cheaper lower RAM card affect the
RAC production?

Thanks, Mike.


G'Day Mike,

Not sure of the 512 MB version but my 1024 MB 4870 is getting over 60,000 cobblestones by itself (so you can see where most of my RAC is coming from).

I doubt that the 512 MB version would be too much different to this, probably depends on how many threads (WUs) you try to run at the same time, I only run 3 at a time (the default setting).
45) Message boards : Number crunching : Milestones II (Message 27996)
Posted 19 Jul 2009 by Profile Conan
Post:
Amazing, 5,000,000 cobblestones on MilkyWay, love that ATI 4870.

Also 13,000,000 cobblestones will be reached in Boinc Total as of 20/7/09.

Congratulations to all other milestone makers.
46) Message boards : Number crunching : Zero credit (Message 27825)
Posted 15 Jul 2009 by Profile Conan
Post:
This series crunches just fine for me, no errors at all, proper credits issued. No reason not to like them!!



G'Day Beau,
Yes nearly all mine also process OK and I can like them. It is an annoying few that we manage to catch (due to the almost instant database purge) that we are talking about.
As you would most likely not be able to see all your work units that get processed, you may not be aware of how many are not getting credit, just as we are not really sure how many fail as they are purged before we can see them.

But as reported a lot have been seen and we are trying to alert the project about it, seeing as they are all from the same WU series.
47) Message boards : Number crunching : ALERT MILKY DATABASE IS DOWN (Message 27568)
Posted 12 Jul 2009 by Profile Conan
Post:
ALERT !!

Milky servers are down.
Database has a problem of connection.

unable to D/L ou U/L jobs


Just uploaded some work and got another 8 WUs in return.
48) Message boards : Number crunching : Zero credit (Message 27566)
Posted 12 Jul 2009 by Profile Conan
Post:
I am also seeing them on my GPU as well.
So far all have been 'ps_sgr_210F5_s3' type WUs and all that I have seen have been on Windows machines.
I have not seen them on my Linux machines.

Agree with Banditwolf, scrap that series and move on.
49) Message boards : Number crunching : Has anyone gotten CUDA WUs ? (Message 27088)
Posted 5 Jul 2009 by Profile Conan
Post:
I have never receive CUDA WUs since I join Milkyway_GPU in May 24, 2009.

It always say "Server error: feeder not running".


And it will keep saying that. no CUDA capable application has been released yet. It is still being worked on.
There are numerous threads on Milkyway about this.
Travis is even considering not going ahead with the GPU site if the server can handle the current work for Milkyway and the GPU app.

The only GPU you can use at the moment is an ATI 38, 45, 47, 48 series cards (I think that was all of them) and use the optimised app 0.19f to get normal Milkyway apps.

If you read some of the other threads you can get more information.
50) Message boards : Number crunching : Configuring BOINC (Message 26728)
Posted 30 Jun 2009 by Profile Conan
Post:

You should really set the avg_ncpus value higher. That way a lot less WUs are loaded and also the time-out issue is no longer present. If you loose one or two tasks is not much of an issue with a Core i7 because of the hyperthreading. And if you really want to avoid it use the cc_config.xml to raise the number of CPUs the BOINC client sees. If you set it to 9 and adjust your MW resource share to 11.1% (1/9) you can more or less reserve one of the 9 CPUs for MW and can afford a lot higher avg_ncpus values (you can even set it to 1.0). At least if you reset the debts it works quite well here.

But generally speaking the scheduler of the BOINC client is quite a mess in my opinion. The features of the newer clients (6.x.xx) like fractional CPU allocation are simply not working as they should.


Where is the cc_config.xml located. I'm running windows7, have change to Boinc 6.6.20 and catalyst to 9.5 from 9.6. It is running better but still tweaking.


It's not located anywhere until you create it. You then place it in the same directory as your Application Data.

Read this thread for more detail.
51) Message boards : Number crunching : More Invalid wu's (Message 26599)
Posted 27 Jun 2009 by Profile Conan
Post:
I have only noticed a few of these faulty work units.

So far all the ones I have caught have been on my Pentium 4 Windows machine and each time the Work Unit in question has been a "ps_sgr_210F5_3s_hiw_" type.

Instead of running for 1 1/2 to 2 hours as normal they run for up to 8 hours.
Always finish and don't error out during whilst running, but I aborted one at 5 1/2 hours last night and another ran for over 8 hours after I had gone to bed, giving zero credit as classed as invalid.

Have probably had more but work units don't hang round all that long.


Just killed another one of these 210F5_3s work units at over 5 hours run time.
Interesting that the reported result shows Zero CPU time not the 5 hours I have been running.

My output on this P4 has dropped a lot recently and i now put it down to this same WU type that is taking so long to run and then gives Zero Credit for the effort, so I know I am getting more than the couple that I have been able to catch.
52) Message boards : Number crunching : More Invalid wu's (Message 26424)
Posted 25 Jun 2009 by Profile Conan
Post:
I have only noticed a few of these faulty work units.

So far all the ones I have caught have been on my Pentium 4 Windows machine and each time the Work Unit in question has been a "ps_sgr_210F5_3s_hiw_" type.

Instead of running for 1 1/2 to 2 hours as normal they run for up to 8 hours.
Always finish and don't error out during whilst running, but I aborted one at 5 1/2 hours last night and another ran for over 8 hours after I had gone to bed, giving zero credit as classed as invalid.

Have probably had more but work units don't hang round all that long.
53) Message boards : Number crunching : Hanging Work Units (Message 26007)
Posted 19 Jun 2009 by Profile Conan
Post:
Have also caught a WU that hung on my GPU

WU completed.
CPU time: 7.875 seconds, GPU time: 25267.7 seconds, wall clock time: 25561 seconds,

Mine appears to have been caused by BOINC allocating too many resources to other projects that I run and did not leave enough CPU power to run the GPU, so it did not do anything for about 7 hours.

It had started and said it was running but all that was happening was the time to completion keep ticking over.

As soon as I suspended a couple of WUs Milkyway started and completed all work it had in the queue, including the 7 hour WU (got a mighty 10 cr/h for that one).

Now I have the unfortunate circumstance of the LTD saying Milkyway has to owe other projects and now I can't get any work. I might have to micro manage BOINC for a while, running Einstein, Docking, AQUA, Ralph at the moment.

Conan.
54) Message boards : Number crunching : Milestones II (Message 25417)
Posted 14 Jun 2009 by Profile Conan
Post:
Have passed 2,500,000 cobblestones.

This is the most I have done in any single project.

Have also passed 10,000,000 cobblestones Total in all BOINC Projects.

Milkyway really helped in getting pass that milestone.
55) Message boards : Number crunching : this site has been slow (Message 25093)
Posted 11 Jun 2009 by Profile Conan
Post:
Have only noticed this in the last hour.
if I click on a message, I have to back out to the home page and then come back in and all loads almost like normal, fairly fast.

This only works for that one message.
The next message I have do the same and back out to the home page then come back in.
Takes a while to read the messages this way though.
56) Message boards : Number crunching : new joking WU-size/type ps_new_11 and ps_new_13 (Message 25086)
Posted 11 Jun 2009 by Profile Conan
Post:
But they gave good credit....shame I didn't get more of them!


They are still there GG, as I am still getting them.
So far I have seen

ps_new_9_1 runs for 197 to 224 sec on CPU
ps_new_11_1 runs for 185 sec on CPU
ps_new_11_2 runs for 187 sec on CPU
ps_new_11_2 runs for 3 to 4 sec on GPU
ps_new_13_2 runs for 200 sec on CPU
ps_new_13_2 runs for 1 sec on GPU
ps_new_15_2 runs for 112 sec on CPU
ps_new_15_2 runs for 2 sec on GPU
ps_newtest_2 runs for 225 sec on CPU
ps_newtest_2 runs for 3 sec on GPU

ps_new_16_2 runs for 31 to 41 sec on a GPU

The CPU is an AMD Opteron 285 @2.6GHz
and the GPU is an ATI 4870 at standard clock.
57) Message boards : Number crunching : ATI GPU app 0.19f fixes the ps_sgr_208_3s errors (Message 24881)
Posted 10 Jun 2009 by Profile Conan
Post:
Help!
How do I change from 3 WU(default) to 8?
I was running 8 on a 4850 with a quad 6600.
I have read the “read me” file, have tried editing
<cmdline>n8</cmdline> + many variations
but no change still only 3.
I’m obviously doing something wrong, can any one help
PS
Many thanks CP, the improvements are fantastic!


Do you really need 8 ??

I have left mine at the default 3 and my output (thanks to Travis and more work) has gone from an average of 900 to over 8,800 in one day on just the one card.

I also remember Cluster Physik saying that running a heap of threads does not mean you will do more work as it slows all the threads down, and doing 1 to 4 threads will get you the same amount of output as doing many more.
Cluster will correct me if I am wrong I am sure.
58) Message boards : Number crunching : Work Availability? (Message 23909)
Posted 2 Jun 2009 by Profile Conan
Post:
Well Travis, something definitely changed.
I got a series of messages that I have been getting for a while plus one message I don't recall seeing for a number of months now, they go like this

Sending scheduler request: To fetch work
Requesting 154355 seconds of new work
Scheduler RPC succeeded: [Server version 607]
Message from server: No work sent
Message from server: (Reached per-CPU limit of 6 tasks)
Message from server: (Project has no jobs available)
Deferring communication for 1 min 0 sec
Reason: No work from project

Have not seen 'Reached per-CPU limit of 6 tasks' for a very long time.

Unfortunately I have seen all the other messages heaps of times.

But it looks like an improvement, particularly if I can get the message a few more times.

Thanks Travis,

Conan.
59) Message boards : Number crunching : Little help for those using opti apps. (Message 20692)
Posted 27 Apr 2009 by Profile Conan
Post:
Try a P4 and CPDN and you could be going for a year. :)
Even my o/c'd nehalems can take 3 months...


That's interesting, as my Phenom manages a work unit in (give or take) 100hrs.


Depends on the work unit type.

There are about 4 different types to chose from in your preferences from a run time of 15 days to 3 months plus, the 15 day one requires 1.5 GB RAM to run.
60) Message boards : Number crunching : Milestones (Message 19610)
Posted 19 Apr 2009 by Profile Conan
Post:
> Have passed 2,000,000 cobblestones for MilkyWay.
Virtually all done on the CPU (took so long to get the GPU going that there was no work to process, so have gone back to CPU).

Have also passed 9,000,000 cobblestones for BOINC Total.

This is my first 2 million point project.


Previous 20 · Next 20

©2024 Astroinformatics Group