I have a question regarding BOINC's reported cache size in a computers ID page.
Basically the size looks wrong on a couple of my systems.

Example:

I'm running 2 pairs of identical machines running 603 xeons, all HP W6000's, all 1GB ram. 2 are 2.0GHZ, 2 are 1.8GHZ.
One of each pair is running with Hyper Threading off to compare RACredit impact for HT on/off over a few weeks. Can't tell yet, only just started.

The HT on machines report 244.14KB Cache - I assume per core, one real, one virtual.
The HT off machines report 488.28KB Cache - all the cache per core.

That makes sense.

So why does my Dual 5160 (2x3GHz/4MB L2) machine, 2 CPUs, 4 real cores, with 4MB per chip, still only report 244.14KB cache?
Same with my single Quad core X3220 (1x2.4GHz/8MB L2) machine, 244.14KB.

Is it a nonsense? Or is BOINC really only seeing and thus using 1/8th what it should be on those 2 systems?
All the systems are running Rosetta & LHC BOINC 50/50 share. LHC also reports same as above.
Is it a BOINC setting I've missed?
Not found anything on the boards so far.

Any thoughts welcome.

The BOINC client is having some trouble retrieving accurate cache figures for all platforms. What BOINC version are you running?

While systems with large L2 cache seem to run Rosetta workloads much better then those without, the system does not use this information in determining what work to send, nor credits to issue. So, at this point, it's basically just shown as further information (sometimes inaccurate) about the host.

---

Rosetta Moderator: Mod.Sense

Thanks for the post.

So, it sounds like there's no bottle neck on my higher end cpus, just an information gathering error?

Not sure what version clients until tomorrow (systems@work) but they were all downloaded from the BOINC Win XP download site in the last 2/3months, one (the the Quad cpu) was downloaded yesterday.

So, it sounds like there's no bottle neck on my higher end cpus, just an information gathering error?

Exactly. It's not like the client could control how much cache to use as it runs. The hardware works that out and controls it. So, it's not like it's trying to live in a small cache when a larger one is actually available.

You can (also) see the BOINC version in the details of your completed tasks.

---

Rosetta Moderator: Mod.Sense