Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => General Internet News => Topic started by: Red_Melons on March 24, 2006, 05:55:02 PM
-
Distributed Amiga has been pushed down into fourth place by the AnandTech 10635 team. Distributed Amiga had overtaken AnandTech 10635, who responded by dramatically increasing their block count.
Distributed Amiga Team Stats (http://stats.distributed.net/team/tmsummary.php?project_id=25&team=200)
If you'd like to see Amiga back in 3rd place, then please join the Distributed Amiga team and ensure that your dnetc client is working only on OGR-P2
-
and in plain english that means...?
-
I would like to know what that means too.
-
Distributed Net FAQ (http://faq.distributed.net/cache/1.html)
-
It means...
START CRUNCHING
Ok Red .. you persuaded me.
I'll change the emphasis from RC72 to OGR (if I can remember how)
-
I guess I need to crank the Amiga back up.
Damn PC ain't gettin' the job done. ;-)
C Snyder
-
Wow... The second I turn my PC to RC-72, we get bumped lol, I switched to OGR now.. Heh..
-
How do I join this, can I just use my P4 to do this ?
My Miggymiga would not stand up to it :)
-
Is is proper to use the Amiga client on AmigaForever, or an emulator? My unreplaceable Amiga hardware is much too valuable to be left on all the time. :) Until the new AmigaOne hardware becomes available. :D - Lars
-
I suppose you could use an amiga client on Winuae/Amiga Forever but you would lose a fair bit of CPU grunt to the emulation.
I have loaded the W32 version, and i have churned 2 lots of jobs.. Make sure you Config up properly.
In the config, go to option 2 (Buffer and Buffer update options, select 9 (load-work precedence) and make sure it reads "OGR-P2, RC5-72=0" (The =0 IS IMPORTANT, without it, it will complete a job on OGR, then switch to RC5), this command TELLS the client to IGNORE RC5.
I cannot get into stats to join Amiga team, as stats site is down.
-
I suppose you could use an amiga client on Winuae/Amiga Forever but you would lose a fair bit of CPU grunt to the emulation.
I have loaded the W32 version, and i have churned 2 lots of jobs.. Make sure you Config up properly.
In the config, go to option 2 (Buffer and Buffer update options, select 9 (load-work precedence and make sure it reads "OGR-P2, RC5-72=0" (The =0 IS IMPORTANT, without it, it will complete a job on OGR, then switch to RC5)
I cannot get into stats to join Amiga team, as stats site is down.
-
@logicalheart
Is is proper to use the Amiga client on AmigaForever, or an emulator?
Why would you want to do that?
You don't need to run Amiga client to be able to contribute to Distributed Amiga team.
-
Can I just add...
Those running PC platforms... upgrade to the latest "PRE" release. These are quite streamlined compared to the Stable, and on my P4-2.53.. i have gained around 10 Million nodes a second increase of processing.
This could be a reason we have dropped..
-
Thank you for info, whiteb!
Here (on a Pentium M machine) the "PRE" release is around 15% faster than the last stable release available. :-)
-
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
-
Just got my dual P3-450s going, now doing 9.3 million nodes/sec. :-D
-
http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=18390&forum=2#279745
LOL.
They are talking about us.
-
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.
-
I think the sudden upsurge in Team Amiga OGR crunching has just trashed Fritz's Hard drive !!
lol
-
@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.
-
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.
-
@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.