
Quote: Originally Posted by
derekimo

Quote: Originally Posted by
Homeuser66

Quote: Originally Posted by
Albuquerque
Sorry, another post real quick: it occurs to me that the best way to show off your SSD would be to use the built-in WinSat benchmark under Windows 7. It already accounts for the proper thread prioritization and gives you metrics that the other benchmark tools cannot.
When I go to run this, even as an Admin, it just pops up with a black CMD looking box and quickly shuts down...What am I doing wrong here?
You should be entering that in an elevated cmd prompt, not trying to elevate winsat.
Thanks! This worked...I don't know what I was doing wrong before....
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>winsat -v disk
Windows System Assessment Tool
> Command Line 'winsat -v disk'
> DWM running... leaving it on
> System processor power policy saved and set to 'max performance'
> Running: Feature Enumeration ''
> Gathering System Information
> Operating System : 6.1 Build-7601
> Processor : Intel(R) Core(TM) i7 CPU 920
@ 2.67GHz
> TSC Frequency : 0
> Number of Processors : 1
> Number of Cores : 4
> Number of CPUs : 8
> Number of Cores per Processor : 4
> Number of CPUs Per Core : 2
> Cores have logical CPUs : YES
> L1 Cache and line Size : 32768 64
> L2 Cache and line Size : 262144 64
> Total physical mem available to the OS : 11.9 GB (12,875,550,720 bytes)
> Adapter Description : NVIDIA GeForce GTX 470
> Adapter Manufacturer : NVIDIA
> Adapter
Driver Version : 8.17.12.9573
> Adapter Driver Date (yy/mm/dd) : 2012\2\9
> Has DX9 or better : Yes
> Has Pixel shader 2.0 or better : Yes
> Has LDDM Driver : Yes
> Dedicated (local) video memory : 1248.44MB
> System memory dedicated as video memory : 0MB
> System memory shared as video memory : 2815.84MB
> Primary Monitor Size : 1920 X 1080 (2073600 total pixels)
> WinSAT is Official : Yes
> Run Time 00:00:00.00
> Running: Storage Assessment '-seq -read -n 0'
Mode Flags = 0x%08x
Disk Number = 0
Iterations = 1
IO Count = 256
Sequential IO Size = 65536
Random IO Size = 16384
Run[1] Type[0x01080001] Zone[0] - 519.975073 MB/s
Run[1] Type[0x01080001] Zone[1] - 527.649715 MB/s
Run[1] Type[0x01080001] Zone[2] - 503.325934 MB/s
Run[1] Type[0x01080001] Zone[3] - 513.795490 MB/s
Run[1] Type[0x01080001] Zone[4] - 494.654794 MB/s
Run[1] Type[0x01080001] Zone[5] - 516.377409 MB/s
Run[1] Type[0x01080001] Zone[6] - 518.153907 MB/s
Run[1] Type[0x01080001] Zone[7] - 521.404754 MB/s
Run[1] Type[0x01080001] Zone[8] - 526.079467 MB/s
Run[1] Type[0x01080001] Zone[9] - 520.779928 MB/s
Run[1] Type[0x01080001] Zone[10] - 519.573578 MB/s
Run[1] Type[0x01080001] Zone[11] - 524.630668 MB/s
Run[1] Type[0x01080001] Zone[12] - 525.125933 MB/s
Run[1] Type[0x01080001] Zone[13] - 524.208780 MB/s
Run[1] Type[0x01080001] Zone[14] - 523.767843 MB/s
Run[1] Type[0x01080001] Zone[15] - 523.715243 MB/s
> Run Time 00:00:12.60
> Running: Storage Assessment '-ran -read -n 0'
Mode Flags = 0x%08x
Disk Number = 0
Iterations = 1
IO Count = 1000
Sequential IO Size = 65536
Random IO Size = 16384
Run[1] Type[0x01000002] Zone[0] - 300.316778 MB/s
> Run Time 00:00:00.81
> Running: Storage Assessment '-scen 2009 -drive C:'
Mode Flags = 0x%08x
Disk Number = 0
Iterations = 1
IO Count = 9000
Sequential IO Size = 65536
Random IO Size = 16384
Requesting a file of size 1073741824 located at physical offset 0x1bf590
0200.
Are these good numbers?