ok after much deliberation i finally upgraded to windows 7 x64. i have been running windows 7 for over a year. whetstone stayed about clock speed, if it was 3.5 then it was at least a 3500 or so, same with 4.0. after upgrading to 64 bit windows 7, my whetstone dropped below 3000, and my dhrystone dropped almost that many points! is 64 bit having a problem with my processor? i've had it since it was released.

amd phenom 2 x6 thuban 1090t black edition
windows 7 ultimate edition 64 bit
please respond soon.. is this expected, or what?

---

I'm also running Windows 7 Ultimate 64-bit on a 1090T, overclocked to 3.57 GHz (210x17). My benchmark numbers at the moment are Floating-point speed 3552.93, Integer speed 8076.6 million ops/sec. This rig has had the 64-bit OS from its inception, so I don't have any 32-bit benchmark numbers to compare. What I do know is that while the floating-point speed stays pretty constant from one benchmark run to the next, the integer speed has varied by several hundred in either direction, depending I suppose on what else the CPU happened to be doing at the time. You could simply have gotten a bad benchmark run.

The real question is: Have you noticed a corresponding reduction in actual crunching performance. In other words, are WUs taking appreciably longer to crunch under Win7 64-bit than they did under Win7 32-bit?


-- Tony D.

---

Taking purely a wild guess here, but have you tried different drivers for your video card? I know you are using the latest but have you tried different ones? I don't think it would be Windows having issues with your processor, especially Windows 7. Have you performed the same, if at all, tweaks you had on your old machine. Also have you updated to SP1 when you moved to 64 and maybe your old machine wasn't? They are showing from RTM to SP1 on W7 x64 that performance on the video card is about the same in games, but it consistently lower, just not by much. In games is doesn't mean much the differences but I supposed it could cause a lower RAC here. Another thing you need to remember to is you took your machine down for awhile doing the re-installation which could have caused your RAC to drop until your machine catches back up. Good luck figuring it out.

Actually looking at your credits your machine doesn't have a strong return on credits per day, which will cause your RAC to rise and fall.

2/16 - 7,060
2/17 - 474
2/18 - 1,366
2/19 - 6,853
2/20 - 8,117
2/21 - 5,565
2/22 - 2,401
2/23 - 3,923
2/24 - 2,098
2/25 - 832

RAC isn't a constant number due to needing to wait on wingmen to finish their units to validate yours, as well as how long each day you run your machine. It will increase a bit each day as long as you are returning the same amount of units each day and people turn in the second version of your unit for validation. If you don't keep your machine running on a pretty consistent basis then your RAC will fall. Especially changing from 8k one day to 800 and back and forth. My suggestion would be to run your computer for a few weeks and wait on it to stabilize and then you will know within a few thousand about how high you should be running.

And really looking farther into your stats your RAC was consistently climbing till about the 24th/late in the day 23rd and it flat lined out but is still rising. You just need to run your Seti@Home more than randomly if you want it to rise and stay up there.

---

Traveling through space at ~67,000mph!

@-BeNT-,

Great "layman's" explanation of how RAC works. I wish the people who panic when their RAC suddenly plummets after an extended outage would take note. However, the OP was talking about his whetstone/dhrystone numbers; i.e. his BOINC benchmark scores. I'm not sure if video drivers or how consistently one crunches have any effect on them, but the presence or lack of Win7 SP1 might. I'm planning on installing SP1 tomorrow. I'll report back what it does to my BOINC benchmarks.


-- Tony D.

---

@-BeNT-,

Great "layman's" explanation of how RAC works. I wish the people who panic when their RAC suddenly plummets after an extended outage would take note. However, the OP was talking about his whetstone/dhrystone numbers; i.e. his BOINC benchmark scores. I'm not sure if video drivers or how consistently one crunches have any effect on them, but the presence or lack of Win7 SP1 might. I'm planning on installing SP1 tomorrow. I'll report back what it does to my BOINC benchmarks.


-- Tony D.

Opps I totally read him right, but got side tracked, crap! Either way it shows his RAC is actually climbing and the whetstone calculations in BOINC aren't accurate either way, if you benchmark 4 times you will get 4 different results. So nothing has changed, makes me wonder if a difference would be caused using a 32bit BOINC versus 64bit BOINC. Just for a heads up SP1 didn't effect anything on my machine at all.

---

Traveling through space at ~67,000mph!

I have never taken the BOINC benchmark as any meaning level of a system performance. Did you also change version of BOINC when going to the new OS? It could be something in how the scores are calculated between the two platforms. I think the thing to do would be watch the completion times for tasks with the same AR. You could run some of the S@H benchmark kits out there & compare them to others.

In running my machines at work. Where we use ghost images to load up a clean version of the OS for testing I haven't notice much, if any, difference between the two platforms, or running x86 OP Apps on x64 OS's.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

i'm specifically talking about my cpu benchmarks. i dont always run seti, and even when i do, its split between it and world community grid. i like to game, and i will say that my gaming experience has been smoother, overall i'm very happy with windows 7 64. i overclocked my processor just a tad and saw my dhrystone shoot above 10000. i just dont get it. my whetstone is still 3200 per cpu, but my dhrystone shot thru the roof, higher than i EVER got it on 32 bit windows 7, overclocked to 4.0! so maybie its just background processes running now that weren't then, i do have sp1 now, i haven't yet had much of a chance to tweak this os either, so what that one guy said could be my whetsone score's issue. that is the highets dhrystone i've ever gotten, just over 10200 or so. it hasn't updated on my rig yet though :|

i'm not really sure we've hit the problem though. i love this os, especially since i have all the damn drivers now! it didn't have drivers for my sound card, and i couldn't afford to get a new one.. so i waited.

i have updated my graphics card drivers to the appropriate 64 bit nvidia drivers, straight from their website. i just want to do the most i can. i'm at 3.8 at 1.5 volts right now, stable, running in even the most finiky games, such as fallout 3.. but i digress a bit. the cpu is stable, the os seems rock solid, i've updated and updated, i'm not really sure what the problem is

all your answers are very appreciated, even the ones that weren't so usefull :)
thanks and please help me understand the situation :)

---

Taking purely a wild guess here, but have you tried different drivers for your video card? I know you are using the latest but have you tried different ones? I don't think it would be Windows having issues with your processor, especially Windows 7. Have you performed the same, if at all, tweaks you had on your old machine. Also have you updated to SP1 when you moved to 64 and maybe your old machine wasn't? They are showing from RTM to SP1 on W7 x64 that performance on the video card is about the same in games, but it consistently lower, just not by much. In games is doesn't mean much the differences but I supposed it could cause a lower RAC here. Another thing you need to remember to is you took your machine down for awhile doing the re-installation which could have caused your RAC to drop until your machine catches back up. Good luck figuring it out.

Actually looking at your credits your machine doesn't have a strong return on credits per day, which will cause your RAC to rise and fall.

2/16 - 7,060
2/17 - 474
2/18 - 1,366
2/19 - 6,853
2/20 - 8,117
2/21 - 5,565
2/22 - 2,401
2/23 - 3,923
2/24 - 2,098
2/25 - 832

RAC isn't a constant number due to needing to wait on wingmen to finish their units to validate yours, as well as how long each day you run your machine. It will increase a bit each day as long as you are returning the same amount of units each day and people turn in the second version of your unit for validation. If you don't keep your machine running on a pretty consistent basis then your RAC will fall. Especially changing from 8k one day to 800 and back and forth. My suggestion would be to run your computer for a few weeks and wait on it to stabilize and then you will know within a few thousand about how high you should be running.

And really looking farther into your stats your RAC was consistently climbing till about the 24th/late in the day 23rd and it flat lined out but is still rising. You just need to run your Seti@Home more than randomly if you want it to rise and stay up there.

wow, i bet you'd be one heckuva troll. ok anyway, who said anything about RAC?
i'm asking about my whetstone/dhrystone changing so drastically. stick to the convo man.
i run seti when is appropriate for me, i didn't know there was a rule on that, lol. the entire statement is totally moot; i didn't ASK about RAC, i KNOW why it goes up and down, this isn't rac, this is a base cpu benchmark that not only boinc uses, but several other benchmarking programs. i'm specifically asking why my numbers changed. i appreciate your... statement, but actually we're talking apples and oranges. i know what rac is, this isn't that. recent average credit has nothing to do with benchmarks within a set program changing suddently, and signifigantly, i'm attempting to get help, because i'm new with 64 bit operating systems in particular.
please help me with that, thanks.

---

What are you using to run these benchmarks? If I have time at work Monday I'll load it up on some machines and see what I get in both OS's for you.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

YES HAL! HEY HAL!, its the built in benchmark for seti. its under advanced i think.

---

@hal my numbers i've gotten so far:
Windows 7 x86 ultimate edition: (3.5 ghz phenom 2x6 1090BEthuban)
Whetstone: 3553 Dhrystone 8250
on x64 ultimate edition (3.8 ghz phenom 2x6 1090t BE Thuban)
whetstone: 3210 Dhrystone: 10202

Video Card
GTX 260 core 216 (MSI dual frozr OC V2 216 N260GTX)

ram: Gskill Ripjaws ddr 2 800 (1.5v 7 7 7 28t)
Western Digital Cavair Black 750gb (the one with two heads, 32mb cache)

---

Is boinc wrote in 32bit?

Ok lets eliminate and determine a couple of things

have you got the 32bit or 64 bit version of bonic installed? Not sure it will make a difference but worth a try changing to 64bit

have you run the benchmark more than once? did the numbers change and if so by much?

have your crunching times for the cpu lengthened at all?

do you have you preferences set the same as before as its a new install?

Windows has a habit of installing things you did not ask for - check and make sure nothing is grabbing cpu cycles when you run the benchmarks in BM

If you are worried what BM is telling you then run the benchmarks several times - i suspect you will get different results everytime - some markedly so 10% + in some cases

to be honest most people take no notice of the benchmarks as they are meaningless other than giving boinc an approx indication of how fast you pc is

as it uses the dcf and server side completion estimate to decide how much work you get - as you are not running optimised you do not have flops values

by the way upgrading to the lunatics optimised apps for the cpu will give you a lot more performance

---

Tim

Ok lets eliminate and determine a couple of things

have you got the 32bit or 64 bit version of bonic installed? Not sure it will make a difference but worth a try changing to 64bit

have you run the benchmark more than once? did the numbers change and if so by much?

have your crunching times for the cpu lengthened at all?

do you have you preferences set the same as before as its a new install?

Windows has a habit of installing things you did not ask for - check and make sure nothing is grabbing cpu cycles when you run the benchmarks in BM

If you are worried what BM is telling you then run the benchmarks several times - i suspect you will get different results everytime - some markedly so 10% + in some cases

to be honest most people take no notice of the benchmarks as they are meaningless other than giving boinc an approx indication of how fast you pc is

as it uses the dcf and server side completion estimate to decide how much work you get - as you are not running optimised you do not have flops values

by the way upgrading to the lunatics optimised apps for the cpu will give you a lot more performance

kk, i have the seti grabbed at setiathome, so if the base installer is 64, then it is, if not, lol then of corse it isn't.
i am in command of windows. i have used computers since i was a child, and know a thing or two about keeping unwanted services from running. in addition, th is os was just installed, every updated and driver downloaded and updated/restarted, etc. so.. there could be things still needing to be.. optimized.
the BM's that seti uses are kinda standard, so the results should be pretty average. so far after bm'ing multiple times, i get the same 3200 whetstone/10200 dhrystone... so it just might be that its 32 bit on a 64 bit os. thats the thing: i'm new at this.
lunatics? sure thing, i'll grab that asap; though i might be going offline for a while soon. preferences are the same as when i was running 32 bit.
in addition, the crunch time of seti WU's has dropped enough that even i can tell. in some instances i've seen an hour cut off of some runs that were only cpu specific. no difference noticeable on cuda, but i just dont pay attention to that one really, since honestly i know NOTHING about c unified driver architecture... WHAT SO EVER, lol.

hope this helps.
lots of directx updates, i've been installing multiple games. i use steam, but steam wasn't running in the background when i did the benchmark.. i just thought i'd mention it.

---

Is boinc wrote in 32bit?

i dont know much about anything, but from what i understand of it, there are optimized... versions of seti, but the actual seti from the webpage is 32 bit.. just learned that actually. there are MANY different versions of seti though. i dont know much about it but thats what i've heard.

---

wow, i bet you'd be one heckuva troll. ok anyway, who said anything about RAC?
i'm asking about my whetstone/dhrystone changing so drastically. stick to the convo man.
i run seti when is appropriate for me, i didn't know there was a rule on that, lol. the entire statement is totally moot; i didn't ASK about RAC, i KNOW why it goes up and down, this isn't rac, this is a base cpu benchmark that not only boinc uses, but several other benchmarking programs. i'm specifically asking why my numbers changed. i appreciate your... statement, but actually we're talking apples and oranges. i know what rac is, this isn't that. recent average credit has nothing to do with benchmarks within a set program changing suddently, and signifigantly, i'm attempting to get help, because i'm new with 64 bit operating systems in particular.
please help me with that, thanks.

Opps I totally read him right, but got side tracked, crap! Either way it shows his RAC is actually climbing and the whetstone calculations in BOINC aren't accurate either way, if you benchmark 4 times you will get 4 different results. So nothing has changed, makes me wonder if a difference would be caused using a 32bit BOINC versus 64bit BOINC. Just for a heads up SP1 didn't effect anything on my machine at all.

Nice, you need to learn to read as bad as me.....

---

Traveling through space at ~67,000mph!

Ok fine

if your wu times are coming down i doubt you have much to worry about

as for being in command of windows good luck with that :)

---

Tim

wow, i bet you'd be one heckuva troll. ok anyway, who said anything about RAC?
i'm asking about my whetstone/dhrystone changing so drastically. stick to the convo man.
i run seti when is appropriate for me, i didn't know there was a rule on that, lol. the entire statement is totally moot; i didn't ASK about RAC, i KNOW why it goes up and down, this isn't rac, this is a base cpu benchmark that not only boinc uses, but several other benchmarking programs. i'm specifically asking why my numbers changed. i appreciate your... statement, but actually we're talking apples and oranges. i know what rac is, this isn't that. recent average credit has nothing to do with benchmarks within a set program changing suddently, and signifigantly, i'm attempting to get help, because i'm new with 64 bit operating systems in particular.
please help me with that, thanks.

Opps I totally read him right, but got side tracked, crap! Either way it shows his RAC is actually climbing and the whetstone calculations in BOINC aren't accurate either way, if you benchmark 4 times you will get 4 different results. So nothing has changed, makes me wonder if a difference would be caused using a 32bit BOINC versus 64bit BOINC. Just for a heads up SP1 didn't effect anything on my machine at all.

Nice, you need to learn to read as bad as me.....

no no, i left it there for posterity, i did see your post... i just thought i'd be funny to respond to it lol

---

Ok fine

if your wu times are coming down i doubt you have much to worry about

as for being in command of windows good luck with that :)

still dont know j ack about 64 bit. but yes, almost at the expense of all other os's besides very basic command knowledge of linux.

---

The BOINC core client is what does the benchmarks, and it does come in both 32 and 64 bit Windows versions. If you're still running the 32 bit version, the benchmarks have probably been affected by running under WOW64. OTOH, if you did a 64 bit BOINC install after switching to 64 bit Windows, the benchmarks are different at least partially because it's a different compile of the sources.

                                                                Joe