Einstein not for old machines?
19 Feb 2005 2:27:05 UTC
Topic 187718
(moderation:
I have been running Einstein for several weeks now and have noticed a pattern with my 500 mhz machine. The workunits that have been completed generally run about 135 credits. I have been consistently getting about 85 credits once validated. I am also running the project on a P4 3.2 H/T processor and on that machine, the workunits and credits granted have been in the 85 to 90 range.
What is it that makes the workunits run so much longer (after adjusting for processor speed) on the old machine? I am also running SETI on that same old machine and have not experienced that magnitude of credit requested/granted disparity. Since Einstein runs so inefficiently on that machine, I will likely detach the project and just run Einstein on my newer machine.
Has anyone else noticed this issue?
Einstein not for old machines?
)
> I have been running Einstein for several weeks now and have noticed a pattern
> with my 500 mhz machine. The workunits that have been completed generally run
> about 135 credits. I have been consistently getting about 85 credits once
> validated. I am also running the project on a P4 3.2 H/T processor and on that
> machine, the workunits and credits granted have been in the 85 to 90 range.
>
> What is it that makes the workunits run so much longer (after adjusting for
> processor speed) on the old machine? I am also running SETI on that same old
> machine and have not experienced that magnitude of credit requested/granted
> disparity. Since Einstein runs so inefficiently on that machine, I will likely
> detach the project and just run Einstein on my newer machine.
>
> Has anyone else noticed this issue?
>
How big is your L2 cache? I have heard problems on other projects where the L2 size makes a huge difference in the CPU time required.
BOINC WIKI
> How big is your L2 cache?
)
> How big is your L2 cache? I have heard problems on other projects where the
> L2 size makes a huge difference in the CPU time required.
>
Sadly, I haven't a clue. According to their website, Intel made processors with both 256K and 512K L2 caches and I'm not sure what specific processor I have.
> > How big is your L2 cache?
)
> > How big is your L2 cache? I have heard problems on other projects where
> the
> > L2 size makes a huge difference in the CPU time required.
> >
>
> Sadly, I haven't a clue. According to their website, Intel made processors
> with both 256K and 512K L2 caches and I'm not sure what specific processor I
> have.
>
Get this... http://www.cpuid.com/cpuz.php
It's small, free and will give you all that sort of info.
My PII Deschutes 266Mhz w/ 512 L2 recently managed to return an E@H w/u and get it validated! This seems to be pretty close to what you are saying.
Date - 15 Feb 2005
Server State - Over
Outcome - Success
Client State - Done
CPU secs - 269,272.48
Claimed - 128.73
Granted - 83.79
I also have a PII Dixon 397Mhz w/ 256 L2 which seems quite a bit faster (relative to the 266) but due to some early problems it's 45 cpu hours away from finishing it's first E@H w/u so I don't have numbers for it yet.
> Get this...
)
> Get this... http://www.cpuid.com/cpuz.php
> It's small, free and will give you all that sort of info.
Neat tool! Thanks!
Ran it and the processor I have does have the 512K L2 cache. Would this be the problem then?