Looking at your WUs, one thing that doesn't make sense is while some report the stock 2.4GHz, others are reporting well in excess of 3GHz... That's a bit odd, and I'm not quite sure what that means just yet, perhaps you're running at stock speed but with reduced multiplier? that would OC the RAM/FSB wouldn't it?

Jason

I've seen a few odd reporting incidents on my 9450, here's a cut-out example:
CPUID: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Speed: 4 x 3446 MHz
Cache: L1=64K L2=6144K
Features: MMX SSE SSE2 SSE3 SSSE3

Here's the normal display:
CPUID: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Speed: 4 x 3280 MHz
Cache: L1=64K L2=6144K
Features: MMX SSE SSE2 SSE3 SSSE3

I haven't been playing around with the speeds at all lately, aside from backing off a little while back, so the higher reported speed is interesting.

-Dave

I have seen CPUZ mess up and misreport the cpu speed occasionally even when locally called.........

This is from the results on my computers page, not CPUz... If it sticks around long enough, here is the over-speed-reported one I cut and pasted from below...

---

I've seen a few odd reporting incidents on my 9450, here's a cut-out example:
CPUID: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Speed: 4 x 3446 MHz
Cache: L1=64K L2=6144K
Features: MMX SSE SSE2 SSE3 SSSE3

Here's the normal display:
CPUID: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Speed: 4 x 3280 MHz
Cache: L1=64K L2=6144K
Features: MMX SSE SSE2 SSE3 SSSE3

I haven't been playing around with the speeds at all lately, aside from backing off a little while back, so the higher reported speed is interesting.

-Dave

The function called to determine CPU speed is ippGetCpuFreqMhz and is provided by Intel...

Here is that functions description...

The function ippGetCpuFreqMhz is declared in the ippcore.h file. This function estimates
the processor operating frequency and returns its value in MHz as an integer stored in
pMhz.
Note that no exact value of frequency is guaranteed so that the estimated value can vary
depending on the processor workload.

Hope this helps,
JDWhale

---

The function called to determine CPU speed is ippGetCpuFreqMhz and is provided by Intel...

Here is that functions description...

The function ippGetCpuFreqMhz is declared in the ippcore.h file. This function estimates
the processor operating frequency and returns its value in MHz as an integer stored in
pMhz.
Note that no exact value of frequency is guaranteed so that the estimated value can vary
depending on the processor workload.

Hope this helps,
JDWhale

I guess that makes some sense, I've just always seen it under-reported up until now (which I assumed could be thermal throttling), it's only since using the AK port that I've seen it over-reported (EXCEPT: when I have the multiplier lower than standard, ie. 8 for a Q6600 - in that case it seems like the function assumes stock multiplier when figuring out the frequency, but that's not the case with this particular instance, it's at the stock multi).

-Dave

---

Hi All,

Brief background:- I'm very interested in the seti@home project and will keep crunching, but I'm so very busy in real life at the moment that I've been "out of the loop" when it comes to checking out updates to the BOINC app and the optimised apps etc...

I'm also not up on the recent discussions on these forums, but I do try to check things out every few months or so to avoid getting too far behind the latest client versions. I certainly don't want to be one of those contributers who screws up the credits for other users by running an ancient client version as I know that really irks some folks!

Anyway, now I realise it is now time for me to change over from the KWSN apps to the new AK apps, and also upgrade to the latest BOINC client at the same time. (I'm going from 5.8.x to 5.10.x)

I have just performed my first update and migration to AK V8 on a SSSE3 system - that has gone flawlessly and it appears to all be running fine. I will shortly do the same on my other SSE3 systems.

However I also have some older systems (SSE/SSE2/MMX), mainly AMD. Can anyone tell me if the older 2.4V app versions on Crunch3r's page (which supports these older CPUs) are typically faster than the KWSN app on AMD CPUs? If so I will migrate these systems over to the 2.4V apps too. In fact I want to do this, as I would like to update to the latest BOINC client on all systems. Do the 2.4V apps work with BOINC 5.10.45?

Thanks very much for any possible advice!

---

Hi All,

...


However I also have some older systems (SSE/SSE2/MMX), mainly AMD. Can anyone tell me if the older 2.4V app versions on Crunch3r's page (which supports these older CPUs) are typically faster than the KWSN app on AMD CPUs? If so I will migrate these systems over to the 2.4V apps too. In fact I want to do this, as I would like to update to the latest BOINC client on all systems. Do the 2.4V apps work with BOINC 5.10.45?

Thanks very much for any possible advice!

The primary difference between 2.4V and the KWSN apps is that the 2.4V (V=Vista) apps are Vista tolerant. The difference in speed for corresponding apps is minimal.

[edit]If you're using XP, then use the one that matches your cpu best. If you're using Vista, by all means use the proper 2.4V app.[/edit]

The primary difference between 2.4V and the KWSN apps is that the 2.4V (V=Vista) apps are Vista tolerant. The difference in speed for corresponding apps is minimal.

Thanks for the speedy reply!

I was using Vista for a while, but I'm now back on XP again due to needing to use some legacy apps, so I don't require the Vista tolerant version at this particular moment.

Therefore, I guess I could keep my 5.8.x BOINC/KWSN setup on those older machines for a while longer. But I may migrate to 5.10.45 anyway just for the sake of keeping things up to date.

I now realise this question is probably off-topic in this particular thread, but briefly, do you know if the 2.4V apps would work fine under BOINC client version 5.10.45? Thanks Again.

---

I now realise this question is probably off-topic in this particular thread, but briefly, do you know if the 2.4V apps would work fine under BOINC client version 5.10.45? Thanks Again.

I tried it. The 2.4V MMX app initially appears to run fine under BOINC 5.10.45. I had forgotten this is a KWSN app.

As I am currently updating my newer systems to AK V8, I am also taking the opportunity to upgrade all of my systems to the latest BOINC client version.

This is regardless of which optimised app each PC happens to use, I just like having them all on the same client version.

Regards, benkid

---

I now realise this question is probably off-topic in this particular thread, but briefly, do you know if the 2.4V apps would work fine under BOINC client version 5.10.45? Thanks Again.

Yes.

I now realise this question is probably off-topic in this particular thread, but briefly, do you know if the 2.4V apps would work fine under BOINC client version 5.10.45? Thanks Again.

Yes.

Thanks for the confirmation. Indeed, I've been running one instance each of the 2.4V MMX, SSE and SSE2 versions on three different machines since last night. I've upgraded all six of my PCs to BOINC 5.10.45 and all are running well. I'm also glad that my three newer machines are now running the faster AK V8 SSE3 or SSSE3 apps without any problems.

---

Mr. Whale, to gain stability on the q6600, I had to install the newest version of Boinc along with AK_v8_win_SSSE3x, since then my averages have started to show increased performance.

Thank you for your efforts.

Hi, after installing this AK_v8_win_SSSE3x on my quad q6600, my computing averages have decreased. Any thoughts on this?

Thanks

Looking at 2 results with similar Angle Range(AR) from before and after switching.... I see that your CPU time has gone from ~6800 to ~3800.

Yes your CPU times have decreased, as expected by ~44% at this AR...

So where is the problem?

Regards,
JDWhale

---

I've upgraded all six of my PCs to BOINC 5.10.45 and all are running well.

I had one final problem, now fixed.

Two of my machines at work are behind a HTTP proxy.

BOINC 5.10.45 doesn't seem to work correctly using FreeProxy 3.92 BUILD 1392, although BOINC 5.8.16 was always fine with it. The problem was that the new BOINC client would report the seti@home server as returning "no header, no data", yet it could see the reference site OK, and reported that the server was down.

I determined that this was purely a problem with FreeProxy, and not with the latest BOINC version. Simply upgrading to FreeProxy 4.00 beta completely fixed this problem.

Perhaps this info would be useful to anyone who is currently updating their BOINC setup and uses FreeProxy.

---

Hi All,

I'm now happily crunching with the AK V8 app for several days! No problems so far, beside a overheating problem of my CPU & MB which is fixed now.

As we've a small 'heat wave' in The Netherlands (temperatures of 27C+, while in southern Europe it's only 20C i've had to improve the cooling of my system.

After the installation of the AK V8 app the Intel E600 dual core of my 'primary' Windows Vista system went too hot, so I immeditely bought an Zalman CNPS9700 at a local store (the only fan in stock). The temperature of the E6600 decreased with about +/- 10C so i couldn't resist to upgrade with a quad-core Q6600 :-)

Although I've a crappy computer case (bad air circulation, need to buy a rear fan) the AK V8 app is now running smoothly 24/7 on my Q6600 :-)

My latest BOINC graph:



Iw@n

---

So far on an AMD Turion 64 X2 @ 1.6 Ghz running the SSE3 app I have the following:

This is a graph of CPU time vs angle range



This is a graph of credit per CPU hour vs angle range



This is credit claimed per processing time along with a linear fit of a line with a fixed y-intercept at 0



There are about 150 datapoints on each graph...

So far on an AMD Turion 64 X2 @ 1.6 Ghz running the SSE3 app I have the following:

This is a graph of CPU time vs angle range



This is a graph of credit per CPU hour vs angle range



This is credit claimed per processing time along with a linear fit of a line with a fixed y-intercept at 0



There are about 150 datapoints on each graph...

Impressive graphs how did you get them using Microsoft sql?

---

Could people please remove the [img] links, when replying to posts with heavy graphical content? This is a popular and busy thread, and repeated graphs make it difficult to load and navigate.

Also, please remember that not everyone has a large or widescreen monitor, and very wide graphics make the whole thread difficult to read.

Another solution is to use an image hosting site which generates linkable preview thumbnails, like Fred has used here. You need to include the direct link as well, because some users have problems with the thumbnail links, but that way the thread is kept small and quick to load, but the fine details and small print are available for people who are interested.

So far on an AMD Turion 64 X2 @ 1.6 Ghz running the SSE3 app I have the following:

This is a graph of CPU time vs angle range
[img][/img]


This is a graph of credit per CPU hour vs angle range
[img][/img]


This is credit claimed per processing time along with a linear fit of a line with a fixed y-intercept at 0
[img][/img]


There are about 150 datapoints on each graph...

http://abrau.durso.googlepages.com/sah_boinc07.xls[/url]


Impressive graphs how did you get them using Microsoft sql?

I used Boinc Log X (an addon program) to gather the AR and time data. It runs in the background and creates a CVS file. Then I manually went to the 'task' website and copied and pasted the amount of claimed credit.

I ended up with this excel worksheet: http://abrau.durso.googlepages.com/sah_boinc07.xls

---

Hi all,

I am running AK opt app SEE3 (64bit amd/intel), wingman is running stock app. My Wu is canonical result, both WU are valid vs each other and get claimed credit.

See this WU 263778712

I look at results of each Wu and I see my wingman reports

Spike count: 2
Pulse count: 0
Triplet count: 4
Gaussian count: 0

yet my result reports

Spike count: 0
Pulse count: 0
Triplet count: 0
Gaussian count: 0


I did have un expected restart [edit](not because of the app) [/edit]... Small issue with the app I am running writing to stderr?

No issue as I got full credit for computer work ... (joking of course)

my real ? is if my result is canonical result does the result get recorded in the DB as result 0,0,0,0 for above when as per my wingman, there might be something there. As in for the next stage of processing would the result of this WU just get passed up because of seemingly 0,0,0,0 result? (I have to assume that we both have same real results, so I would hope not and this is just a clitch with output to stderr)

Sorry if this has been asked before.

Kind Regards

---

Hi all,

I am running AK opt app SEE3 (64bit amd/intel), wingman is running stock app. My Wu is canonical result, both WU are valid vs each other and get claimed credit.

See this WU 263778712

I look at results of each Wu and I see my wingman reports

Spike count: 2
Pulse count: 0
Triplet count: 4
Gaussian count: 0

yet my result reports

Spike count: 0
Pulse count: 0
Triplet count: 0
Gaussian count: 0


I did have un expected restart [edit](not because of the app) [/edit]... Small issue with the app I am running writing to stderr?

No issue as I got full credit for computer work ... (joking of course)

my real ? is if my result is canonical result does the result get recorded in the DB as result 0,0,0,0 for above when as per my wingman, there might be something there. As in for the next stage of processing would the result of this WU just get passed up because of seemingly 0,0,0,0 result? (I have to assume that we both have same real results, so I would hope not and this is just a clitch with output to stderr)

Sorry if this has been asked before.

Kind Regards

It's good you brought it up. The code base from which Alex worked was branched from the project sources at 5.13, and at that time the individual counts of found signals were not written to the checkpoint file. That means the counts in stderr will only show the number of signals found since the last restart. I know Jason hopes to do some more tuning of the ported apps, we'll try to get some of these cosmetic issues cleaned up for any future updates.

It's a cosmetic issue because what gets put into the master science database is the canonical uploaded result file chosen by the Validator, the stderr data is merely included in the report sent to the Scheduler so users have something to look at.

                                                               Joe

It's good you brought it up. The code base from which Alex worked was branched from the project sources at 5.13, and at that time the individual counts of found signals were not written to the checkpoint file. That means the counts in stderr will only show the number of signals found since the last restart. I know Jason hopes to do some more tuning of the ported apps, we'll try to get some of these cosmetic issues cleaned up for any future updates.

It's a cosmetic issue because what gets put into the master science database is the canonical uploaded result file chosen by the Validator, the stderr data is merely included in the report sent to the Scheduler so users have something to look at. Joe

Thanks for the reply Joe, was as I hoped.

Regards

---

We will see soon SSE and MMX AK V8 also?


(100. post in this thread!)

---