Matroxusers@ClimatePrediction.net

[westonez]

I'll help too

[bsdgeek]

westonez:

[GNEP]

welcome aboard!

[bsdgeek]

It is done.

[GNEP]

Thanks bsd

[GNEP]

Well pop-pickers, we have made our entry to the top 40, coming straight in a #39! Thanks for the group effort

[M|x]

i just signed up

[Fluff]

#37 Now, Just above Overclockers UK and a touch below Canada

God this program seriously slows down outlook everything else is fine... raptor666

[GNEP]

Odd that it apparently slows down outlook...no probs with Mozilla mail. I know this client has more disk access going on than other distributed projects, so perhaps running the model off a different HDD or defragging might help?

Good news that we're continuing to rise as a team though

EDIT: and collectively we've managed over 200 model years now! Woohoo!

[Fluff]

I think that the task of synchronising with an exchange server in outlook is of a lower priority than the climate prediction software, i just pause it when doing a send recieve and it goes 10x faster.

Peter

Maybe one of my machices will complete phase 1 soon

[GNEP]

Well you are fair flying along... won't be long until you pass me But then I've already finished a phase 1

[M|x]

its going rather slow over here. 3.24% of fase one. running @ 1.1ghz athlon

[GNEP]

Well as a comparator, my Athlon XP 2000+ does just over 1.2 model years per real day (24hrs) if running at 100% (whilst I'm using it for other stuff at times, so this isn't too accurate).

My Duron 1200 on the other hand does about 0.5 model years per real day - it doesn't do much other than crunch and deliver the odd webpage so I have more faith in this number. You can work it out using the "trickle" information on your stats pages.

(As there are 45 years over the 3 phases, 1 model year is 2.2222...% of the total, or 6.6667% of each phase. Your first trickle happens about timestep 10850 or so, at 1.4% of phase one, or 0.628 model years)

How long have you been running it?

[Jon P. Inghram]

Don't forget the CPU time the client reports to the stats page is just the total time the client has been running, not the total time the client actually has spent processing. Thus if you left it up for 6 hours, but had something else that was using 100% of the CPU you'd still get 6 hours of time showing up on the stats even though the climate client didn't get any CPU time.

[GNEP]

Yup - hence the inaccuracy of my Athlon numbers above...