TPU's WCG/BOINC Team

[librin.so.1]

What is CPU-G?

 

[hat]

cpu-z for loonix

 

[brandonwh64]

Can anyone give me some suggestions on what could be the deal with this I7-920? Yesterday I only posted 1,327 for it and then the day before was even worse 897.... 8 Threads should atleast clear 3500 a day right?

 

[librin.so.1]

>On multiprocessor systems, use at most 0.00% of processors.
lolwut.

 

[brandonwh64]

>On multiprocessor systems, use at most 0.00% of processors.
lolwut.

Show it be something different?

 

[librin.so.1]

It should be 100.00% (one hundred percent). Though, I suppose 0.00% defaults to "all".
But You know how they say: better be on the safe side.

 

[brandonwh64]

It should be 100.00% (one hundred percent). Though, I suppose 0.00% defaults to "all".
But You know how they say: better be on the safe side.

I changed it to 100% so hopefully that helps some. Its taking about 4 hours a WU but what is the average time it should take? Its been a long time since I ran a 8 thread I7-920 under WCG

 

[[Ion]]

Yes, I would say that 3-3.5k PPD should be a reasonable estimate. My 3612QM is faster clock-for-clock but at at about the same speeds can pull down 3.8-4k running 24/7.

 

[brandonwh64]

are you running version 7.0.64?

Also am I running the right project? This is what I have always ran.

 

[librin.so.1]

Does Your "Projects" tab only contain one entry?

 

[brandonwh64]

Does Your "Projects" tab only contain one entry?

Yes it has this one

 

[librin.so.1]

that looks 100% good.

Also, are You sure Your CPU is running in its full clocks? I've seen some machines where the CPUs would be stuck on the lowest clock, but only for WCG tasks. I suspect that might be the case, as Your 4 hour running time estimate for FAAH units looks definitely wrong.
For FAAH, my FX-8230 @ 3.9GHz has a running time estimate of 01:03 and the 3.6GHz one has 01:18 per WU. So that suggests Your CPU runs at a very low clock.

 

[brandonwh64]

that looks 100% good.

Also, are You sure Your CPU is running in its full clocks? I've seen some machines where the CPUs would be stuck on the lowest clock, but only for WCG tasks. I suspect that might be the case, as Your 4 hour running time estimate for FAAH units looks definitely wrong.
For FAAH, my FX-8230 @ 3.9GHz has a running time estimate of 01:03 and the 3.6GHz one has 01:18 per WU. So that suggests Your CPU runs at a very low clock.

It runs at this 24/7. Speedstep, spread spectrum, Cstates, ALL turned off. Only thing set manual is the ram to 1333 CAS9 T1

 

[[Ion]]

that looks 100% good.

Also, are You sure Your CPU is running in its full clocks? I've seen some machines where the CPUs would be stuck on the lowest clock, but only for WCG tasks. I suspect that might be the case, as Your 4 hour running time estimate for FAAH units looks definitely wrong.
For FAAH, my FX-8230 @ 3.9GHz has a running time estimate of 01:03 and the 3.6GHz one has 01:18 per WU. So that suggests Your CPU runs at a very low clock.

There's also the Linux vs Windows difference--my Opty system with Ubuntu finishes WUs faster than the i7 QM, despite my certainty that a 2.8GHz Ivy Bridge is faster per-thread than a 2GHz Phenom II.

Brandon, try running a few SN2S WUs--I have a better idea of how long they take (as I have the i7-920 doing those).

 

[Norton]

@Brandon- check the # of pending wu's in your WCG account (pending validation and verification). Your rig is just starting off so it will usually build up a backlog of those as it's getting up to speed. Allow anywhere from a few days to a week (or more) for the rig to produce full output. Keep an eye out for invalids/errors as well.

My i7-930 rig is still spooling up and its been running for a couple of weeks now.

 

[[Ion]]

It should definitely have leveled off before a couple of weeks--I've seen that PPD pretty much always arrives at what it will be within a week or so. Sure, still some day-to-day variation, but it's within what it will end up as.

Brandon, you can also check out the Device Statistics page--your i7 system should be pulling in nearly 8 days of runtime/day--if it's much less, it's still spooling up as Norton said.

 

[brandonwh64]

I have about 2 pages of pending validations but they are only for the 8/31?

 

[[Ion]]

If you click on the device name then you can see the points/WUs/runtime that it's done each day--this will be most informative

 

[brandonwh64]

 

[[Ion]]

Yeah--that doesn't look right. The nine hours of runtime yesterday indicates that there are a lot of WUs that aren't yet validated (or threw errors) and the 2.7 days the day before and even the 4.3 days still are far less than you should be seeing. If you check the Results Status page, do you see a lot of WUs that were marked as invalid/errored?

 

[brandonwh64]

Yeah--that doesn't look right. The nine hours of runtime yesterday indicates that there are a lot of WUs that aren't yet validated (or threw errors) and the 2.7 days the day before and even the 4.3 days still are far less than you should be seeing. If you check the Results Status page, do you see a lot of WUs that were marked as invalid/errored?

I have 0 on both errored and invalid

 

[xvi]

Yep. Was going to say check for invalid results.

Edit: Let it spool then.

 

[ThE_MaD_ShOt]

My 920 is pulling around 5k ppd. Mine is also running at 3.5. I suspect your lower clocks aren't helping any but you should be alot higher then you are. Also the last couple days I have seen a drop in ppd out of my 8350 rig so it maybe a wcg thing.

 

[hat]

Maybe this? Set it to 0.

 

[HammerON]

When I used to run several i7 920 rigs they would average around 4.5k to 5k at stock clocks. Brandon should be getting something similar...