Ace-a-Rue
02-21-2008, 05:06 PM
man, i have been routinely negative about vista in some respects of what it offers to users...i like some parts of vista and other parts i would like to delete or turn them off....supposedly, speed has been the main complaint from many guys who would bench on vista...not sure how many were using 32 bit or 64 bit.
i set up my Areca Raid card on the IP35 Pro with two Seagate single platter 250 gb drives (7200.10 series)...i partitioned XP SP2 in the very front with 30G's and right after it was a 80G partition with Vista 64 Ultimate installed as a dual boot configuration.
i decided to run (bench) wPrime (here) (http://www.wprime.net/about.html)...it is a short bench lasting between 5-12 minutes depending on how many cores you have....here is a quote about the multi-threading bench:
Technicalities
--------------------------------------------------------------------------------
wPrime uses a recursive call of Newton's method for estimating functions, with f(x)=x2-k, where k is the number we're sqrting, until Sgn(f(x)/f'(x)) does not equal that of the previous iteration, starting with an estimation of k/2. It then uses an iterative calling of the estimation method a set amount of times to increase the accuracy of the results. It then confirms that n(k)2=k to ensure the calculation was correct. It repeats this for all numbers from 1 to the requested maximum.
Threading
--------------------------------------------------------------------------------
Our aim was to make a perfectly threaded benchmark, such that it would consistantly use 100% of the CPU while in use. This is achieved by using the WMI to detect the CPU count and use exactly that many processing threads to avoid any performance losses due to multiple threads running on any single physical thread. Each thread is designed to do 1/n of the work, where n is the number of threads. For example, if you're calculating 16 roots on 4 CPU's, each CPU will calculate 4 roots. Some might argue that this style of threading is unrealistic in real-time performance, but in fact is quite indicative of performance in several real world tasks such as F@H which allows you to run several instances of the work at any one time.
OK...i'll cut to the chase...here it is...not super fast but definitely faster.
i set up my Areca Raid card on the IP35 Pro with two Seagate single platter 250 gb drives (7200.10 series)...i partitioned XP SP2 in the very front with 30G's and right after it was a 80G partition with Vista 64 Ultimate installed as a dual boot configuration.
i decided to run (bench) wPrime (here) (http://www.wprime.net/about.html)...it is a short bench lasting between 5-12 minutes depending on how many cores you have....here is a quote about the multi-threading bench:
Technicalities
--------------------------------------------------------------------------------
wPrime uses a recursive call of Newton's method for estimating functions, with f(x)=x2-k, where k is the number we're sqrting, until Sgn(f(x)/f'(x)) does not equal that of the previous iteration, starting with an estimation of k/2. It then uses an iterative calling of the estimation method a set amount of times to increase the accuracy of the results. It then confirms that n(k)2=k to ensure the calculation was correct. It repeats this for all numbers from 1 to the requested maximum.
Threading
--------------------------------------------------------------------------------
Our aim was to make a perfectly threaded benchmark, such that it would consistantly use 100% of the CPU while in use. This is achieved by using the WMI to detect the CPU count and use exactly that many processing threads to avoid any performance losses due to multiple threads running on any single physical thread. Each thread is designed to do 1/n of the work, where n is the number of threads. For example, if you're calculating 16 roots on 4 CPU's, each CPU will calculate 4 roots. Some might argue that this style of threading is unrealistic in real-time performance, but in fact is quite indicative of performance in several real world tasks such as F@H which allows you to run several instances of the work at any one time.
OK...i'll cut to the chase...here it is...not super fast but definitely faster.