Distributed Amiga pushed down to 4th!

[billchase]

Roughly 16-17% gain on a 2.3Ghz Barton core.  Has anyone posted this
info on amigaworld.net?  I know there are a few crunchers over there as
well.


C Snyder

[kd7ota]

Just got my dual P3-450s going, now doing 9.3 million nodes/sec.  :-D

[whiteb]

http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=18390&forum=2#279745

LOL.

They are talking about us.

[Piru]

It should probably be pointed out that these new improved cores are X86 only, indeed. M68K and PPC cores are already pretty much optimal, so there aren't any new M68K or PPC clients in sight.

[The_Editor]

I think the sudden upsurge in Team Amiga OGR crunching has just trashed Fritz's Hard drive !!

lol

[SHADES]

@sknight

Wooo nice avatar!
I don't suppose you have a larger rendered version I could use for a screensaver on my phone do you? this one is very small.

[boing]

OK, I looked at the site and the software and I'm going to join forces for the name of the Amiga.

But first I have a few questions.

You can run it as a Service or as a normal startup task.

It sounds like installing it as a service means you get it running more full time, even between users logging in, or when the screensaver is going (I have my screensaver set to "none" on XP).

Installing it as a startup task appears to give you feedback about it's progress.  But it also appears that this way, it doesn't run when your screensaver is on unless you screw around a bit.

The implication seems to be that if you install it as a service, you don't get to see any info about what's going on, even in the taskbar.

I'd like the option of seeing what it's doing per a typical install, but installing as a service sounds like it would make better use of free cycles.

Can any experienced pros with the Windows version clue me in?

BTW I'm running a 1.6GHz AMD Mobile Sempron 2800+, 256KB L2 cache, and utterly worthless 1.6GHz FSB. Using 32 version of XP.

[whiteb]

@boing.

I can clear things up for you...  

You can run it as One *OR* the other.

Service mode, you are right, you will not get the pretty graph indicating whats going on
Client mode - pretty graph.

If you run it as a SERVICE, then you have 2 ways to keep track of what its doing..

1) run the service with LOGGING set to output to a SHARED drive.. this tells you in a text format, everything that it is doing, from what packet its working on, to Mnodes a second processing rate.

2) run one of the available Distributed.net proxies.. and pull the stats from that.

The second way, the proxy is more aimed for people with LOTS of clients.. one person on IRC claims to run a proxy for around 200 clients (corporate network), so I would recommend just outputting a LOG from the service to a shared drive, and checking the log when you feel you want to.

I do this for the wife's machine, I just log into the shared drive and check the log.