Hmmm - it should make no difference where the OS was residing or what OS version it was - this is a straight C application that doesn't do any disk I/O and is too small to need to be loaded in segments.
I wonder if your Tiger boot had some other processes running? Like whatever is in Login Items?
Hmmm - it should make no difference where the OS was residing or what OS version it was - this is a straight C application that doesn't do any disk I/O and is too small to need to be loaded in segments.
I wonder if your Tiger boot had some other processes running? Like whatever is in Login Items?
Could be.
Hang on I'll hop over and disable anything and try again ....
hah - you were right !
Two words - "Net Barrier" on the Tiger disc. Interestingly (or not) I had Little Snitch running on the Leopard disc when testing so I'd expect some nano seconds improvement on that score if I disabled it.
PowerBook G4 (17-inch 1.67 GHz) ("PowerBook5,7") with 1 cores, running at 1.67 gHz.
Frontside bus: 166.48 mHz
Installed memory: 1.50 GB
200,000,000 factorials will be calculated by creating 1 threads.
Thread # 1 created.
Waiting for threads to finish...
Thread # 1: 200,000,000 factorials calculated in 31.813558 seconds at 6,286,628 factorials per second.
logout
[Process completed]
Results for my MP 2.66 Quad are straight in line with what others have posted - low 3's.
Und finally
(null) ("iMac7,1") with 2 cores, running at 2.00 gHz.
Frontside bus: 800.00 mHz
Installed memory: 2.00 GB
200,000,000 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 2: 100,000,000 factorials calculated in 8.872523 seconds at 11,270,751 factorials per second.
Thread # 1: 100,000,000 factorials calculated in 8.888610 seconds at 11,250,353 factorials per second.
(null) ("MacBookPro4,1") with 2 cores, running at 2.50 gHz.
Frontside bus: 800.00 mHz
Installed memory: 4.00 GB
2,147,483,647 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 1: 1,073,741,823 factorials calculated in 79.865624 seconds at 13,444,355 factorials per second.
Thread # 2: 1,073,741,823 factorials calculated in 80.862756 seconds at 13,278,571 factorials per second.
Same MacbookPro but a larger benchmark.. seems to scale well
Yep. It is almost linear with CPU clockspeed.
It limited your iterations to 2^31-1 because this is not a 64-bit app. The biggest number that a 32-bit signed integer can hold is 2,147,483,647. I guess I could make it unsigned - then it could count to 2^32-1, which is twice as much.
Anybody have some ideas as how to make it faster like it SHOULD be??? Its only 6 months old.
Checked that. Nothing else running.
The only other explanation is that one of your cores is turned off.
Do both green bars show full blast in Activity Monitor?
The bench just asks the OS how many cores there are - it doesn't test them to see if they are working. And it will make 2 threads even if one core is shut down, and the Mach kernel will just swap the threads on that one core.
This would be rare, but if one of your cores blew out or somebody used BSD to turn it off, then that would explain it. I still think there might be a background process running though.
The only other explanation is that one of your cores is turned off.
Do both green bars show full blast in Activity Monitor?
The bench just asks the OS how many cores there are - it doesn't test them to see if they are working. And it will make 2 threads even if one core is shut down, and the Mach kernel will just swap the threads on that one core.
This would be rare, but if one of your cores blew out or somebody used BSD to turn it off, then that would explain it. I still think there might be a background process running though.
Comments
messiah, how many macs do u own?
Three personally, five total in the household...
...I know!
Frontside bus: 166.48 mHz
Installed memory: 1.50 GB
200,000,000 factorials will be calculated by creating 1 threads.
Thread # 1 created.
Waiting for threads to finish...
Thread # 1: 200,000,000 factorials calculated in 32.257911 seconds at 6,200,030 factorials per second.
logout
[Process completed]
hmm, the above was on Leopard installed on the hard drive - so I booted over into tiger on a fw 400 external.
PowerBook G4 (17-inch 1.67 GHz) ("PowerBook5,7") with 1 cores, running at 1.67 gHz.
Frontside bus: 166.48 mHz
Installed memory: 1.50 GB
200,000,000 factorials will be calculated by creating 1 threads.
Thread # 1 created.
Waiting for threads to finish...
Thread # 1: 200,000,000 factorials calculated in 52.750747 seconds at 3,791,416 factorials per second.
logout
[Process completed]
I wonder if your Tiger boot had some other processes running? Like whatever is in Login Items?
Hmmm - it should make no difference where the OS was residing or what OS version it was - this is a straight C application that doesn't do any disk I/O and is too small to need to be loaded in segments.
I wonder if your Tiger boot had some other processes running? Like whatever is in Login Items?
Could be.
Hang on I'll hop over and disable anything and try again ....
hah - you were right !
Two words - "Net Barrier" on the Tiger disc. Interestingly (or not) I had Little Snitch running on the Leopard disc when testing so I'd expect some nano seconds improvement on that score if I disabled it.
PowerBook G4 (17-inch 1.67 GHz) ("PowerBook5,7") with 1 cores, running at 1.67 gHz.
Frontside bus: 166.48 mHz
Installed memory: 1.50 GB
200,000,000 factorials will be calculated by creating 1 threads.
Thread # 1 created.
Waiting for threads to finish...
Thread # 1: 200,000,000 factorials calculated in 31.813558 seconds at 6,286,628 factorials per second.
logout
[Process completed]
Results for my MP 2.66 Quad are straight in line with what others have posted - low 3's.
Und finally
(null) ("iMac7,1") with 2 cores, running at 2.00 gHz.
Frontside bus: 800.00 mHz
Installed memory: 2.00 GB
200,000,000 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 2: 100,000,000 factorials calculated in 8.872523 seconds at 11,270,751 factorials per second.
Thread # 1: 100,000,000 factorials calculated in 8.888610 seconds at 11,250,353 factorials per second.
logout
[Process completed]
(null) ("MacBookPro4,1") with 2 cores, running at 2.50 gHz.
Frontside bus: 800.00 mHz
Installed memory: 4.00 GB
200,000,000 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 1: 100,000,000 factorials calculated in 7.407347 seconds at 13,500,110 factorials per second.
Thread # 2: 100,000,000 factorials calculated in 7.460093 seconds at 13,404,659 factorials per second.
logout
[Process completed]
./factorialBench 2 4000000000
(null) ("MacBookPro4,1") with 2 cores, running at 2.50 gHz.
Frontside bus: 800.00 mHz
Installed memory: 4.00 GB
2,147,483,647 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 1: 1,073,741,823 factorials calculated in 79.865624 seconds at 13,444,355 factorials per second.
Thread # 2: 1,073,741,823 factorials calculated in 80.862756 seconds at 13,278,571 factorials per second.
Same MacbookPro but a larger benchmark.. seems to scale well
(null) ("MacBookPro3,1") with 2 cores, running at 2.40 gHz.
Frontside bus: 800.00 mHz
Installed memory: 4.00 GB
200,000,000 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 1: 100,000,000 factorials calculated in 13.023079 seconds at 7,678,676 factorials per second.
Thread # 2: 100,000,000 factorials calculated in 13.085910 seconds at 7,641,807 factorials per second.
logout
This does not make me happy...... I don't know why its this slow....
You have some other processes running. Check Activity Monitor.
Checked that. Nothing else running.
N101-Mac:~ Name101$ /Users/Name101/Desktop/factorialBench/factorialBench ; exit;
./factorialBench 2 4000000000
(null) ("MacBookPro4,1") with 2 cores, running at 2.50 gHz.
Frontside bus: 800.00 mHz
Installed memory: 4.00 GB
2,147,483,647 factorials will be calculated by creating 2 threads.
Thread # 1 created.
Thread # 2 created.
Waiting for threads to finish...
Thread # 1: 1,073,741,823 factorials calculated in 79.865624 seconds at 13,444,355 factorials per second.
Thread # 2: 1,073,741,823 factorials calculated in 80.862756 seconds at 13,278,571 factorials per second.
Same MacbookPro but a larger benchmark.. seems to scale well
Yep. It is almost linear with CPU clockspeed.
It limited your iterations to 2^31-1 because this is not a 64-bit app. The biggest number that a 32-bit signed integer can hold is 2,147,483,647. I guess I could make it unsigned - then it could count to 2^32-1, which is twice as much.
You have some other processes running. Check Activity Monitor.
This is What i had Running when i did the test.
Anybody have some ideas as how to make it faster like it SHOULD be??? Its only 6 months old.
Checked that. Nothing else running.
The only other explanation is that one of your cores is turned off.
Do both green bars show full blast in Activity Monitor?
The bench just asks the OS how many cores there are - it doesn't test them to see if they are working. And it will make 2 threads even if one core is shut down, and the Mach kernel will just swap the threads on that one core.
This would be rare, but if one of your cores blew out or somebody used BSD to turn it off, then that would explain it. I still think there might be a background process running though.
Choose "All processes" from the popup, not just user processes.
The only other explanation is that one of your cores is turned off.
Do both green bars show full blast in Activity Monitor?
The bench just asks the OS how many cores there are - it doesn't test them to see if they are working. And it will make 2 threads even if one core is shut down, and the Mach kernel will just swap the threads on that one core.
This would be rare, but if one of your cores blew out or somebody used BSD to turn it off, then that would explain it. I still think there might be a background process running though.
How would I go about turning them on/off?
Wow.. that is just over half my performance.
This is What i had Running when i did the test.
Yeah I don't know what happened. It was lightning fast when I first got it and about 2 months ago I seen the spinning beach ball for the first time.
but this is the 4th day in uptime
and i have working prjects on Morph age and Photoshop
and just a lot of junk that stays open untill i restart my computer.
When i had windows running i would have to do "Program Clean up" to keep it running smoothly.
but mac wow.... just wow i love it.
and to be honest I think i could squeeze a little more points out of the bench mark. if i restarted and then used the program.
but i wonder what is happening with background programs Footloose301
How would I go about turning them on/off?
You have to have the hwprefs BSD tool installed. This gets installed with the CHUD package from the Developer Tools.
Just to check, try typing "hwprefs" in Terminal and see if it knows what the hell you are talking about.
Before you go messing with that though, what about the two green bars in the Activity Monitor? Choose "Floating CPU Window" from the Window menu.
You have to have the hwprefs BSD tool installed. This gets installed with the CHUD package from the Developer Tools.
Just to check, try typing "hwprefs" in Terminal and see if it knows what the hell you are talking about.
Before you go messing with that though, what about the two green bars in the Activity Monitor? Choose "Floating CPU Window" from the Window menu.
Yeah now I've got this thing in the bottom left of my screen with both green bars lighting up.
When typing this, both of them take up 2-3 blocks each. When I run that benchmark they both go completely solid.
You have to have the hwprefs BSD tool installed. This gets installed with the CHUD package from the Developer Tools.
Just to check, try typing "hwprefs" in Terminal and see if it knows what the hell you are talking about.
Before you go messing with that though, what about the two green bars in the Activity Monitor? Choose "Floating CPU Window" from the Window menu.
Hey, $20 paypal if you can figure it out. haha
I have no idea why its moving so slow and its bothering the crap out of me.