I have one boxen on this project. xp2600 :thumbs:
Anyone else wanna 'test the waters'? :cheers:
Printable View
I have one boxen on this project. xp2600 :thumbs:
Anyone else wanna 'test the waters'? :cheers:
what kind of time comittment are we looking at?
is this like gimps where you have to run 2-4 weeks to get one result?
2-3 hrs only not 2-3 weeks. :)
Citrix
:cool: :cool: :cool:
Reminds me of the Prime95 client, only you get faster results. :D
Easy as heck to install...
icon in the systray, plays nicely so far to :)
Not another Project :D
Could do with some decent stats :Pokes:
I'll get a client on it later... and do some stats tomorrow for the few people who are running it :)
Bok
:notworthy
I will put my wife's laptop on it just to see how it runs.
Ray
So which client do we run ?
There are at least three different ones, confused
i downloaded a .zip file from the main page, that is the only one i foundQuote:
Originally posted by PCZ
So which client do we run ?
There are at least three different ones, confused
i put 1 AMD 2100+ onto this
it needs a native service install, i like how simple it is to setup/start
with the switch to tell it to pull 1-100 work thingys, it might make a good sneakernet project with a native service install
I am running the llrnet network client.
What confused me is that there is mention of other clients on the forum.
I done some tests on a few different MB/CPU combos and P4's with fast FSB are the best.
The speed the client processes is directly linked to the memory bandwidth available.
Increasing the CPU speed doesn't make the client process any faster.
I swapped out a P4 2.4 and replaced it with a P4 3.0 and the performance was the same.
On HT P4's running 2 clients is not good because the client loves memory bandwidth.
Best to run a different project on the second virtual CPU.
On my Athlon XP's the performance was poor, even on the Nforce2 MB's with dual channel DDR running at 166mhz FSB.
I don't have access to any Athlon 64's so I can't say how well they perform.
Quote:
Originally posted by FoBoT
it needs a native service install, i like how simple it is to setup/start
with the switch to tell it to pull 1-100 work thingys, it might make a good sneakernet project with a native service install
Use Firedaemon for right now. I will look into it when I get time.
If you just want the client to start up each time you start the computer you can use Regcleaner and add a registry.
Citrix
:cool: :cool: :cool:
the other clients are for other parts of the project. Like sieving, p-1 etc..Quote:
Originally posted by PCZ
I am running the llrnet network client.
What confused me is that there is mention of other clients on the forum.
I done some tests on a few different MB/CPU combos and P4's with fast FSB are the best.
The speed the client processes is directly linked to the memory bandwidth available.
Increasing the CPU speed doesn't make the client process any faster.
I swapped out a P4 2.4 and replaced it with a P4 3.0 and the performance was the same.
On HT P4's running 2 clients is not good because the client loves memory bandwidth.
Best to run a different project on the second virtual CPU.
On my Athlon XP's the performance was poor, even on the Nforce2 MB's with dual channel DDR running at 166mhz FSB.
I don't have access to any Athlon 64's so I can't say how well they perform.
LLRnet does prefer p4's over other machines. Also with HT you need to run 2 processes of LLRnet to take advantage of HT.
For Athlon 64 read this:
http://www.boardpages.com/psp/viewtopic.php?t=50
Also, I personally think that the client speed increases if the CPU speed is increased.
Athlons and non p4 should be used for sieving because they are best at that and p4's on LLRnet as they are best at finding primes.
Citrix
:cool: :cool: :cool:
Quote:
Originally posted by FoBoT
it needs a native service install, i like how simple it is to setup/start
with the switch to tell it to pull 1-100 work thingys, it might make a good sneakernet project with a native service install
Fobot,
Why do you need the native service. If you tell me why then I might be able to modify LLRnet accordingly.
LLR can be hidden right now ( made invisible) , if that is what you want and it can be started at boot up hidden.
Let me know!
Citrix
:cool: :cool: :cool: