Traffic on the current site is heavy and is expected to double in a year.
#Macbook pro menumeters safe how to
Would anyone be able to tell me how to use these commands to test my USB 3.0 drives or Thunderbolt drives?Ī customer wants a new server to dedicate to its latest high-transaction Web app. ioMeter is the best open source benchmarker out there however they don't fully support OSX, just the worker engine binaries - so iometer itself would have to run on a separate machine.
during regular multi application usage of the OS. iow - this is as fast as it gets and in no way indicative of how your drive performs when ~30-50% of its reads and writes are random - i.e. One more thing to add and I don't know if was already mentioned or not tl:dr - this is a sequential test only. Time dd if=/dev/zero bs=1024k of=tstfile count=1024 2>&1 | grep sec | awk ''Īaaah much more like it. …or you can just use a disk benchmarking tool like bonnie, which is available to be installed from MacPorts. I wonder, though, if I should be getting higher speeds. Yes, the WD My Book is a bit slower, but it has no fan, which is a big plus. It's much faster than the internal SSD in my 2011 iMac. Using RAID0, I get around 450MB/s read and 360MB/s write speeds with every test I've tried. I bought a Factory Refurb LaCie Little Big Drive for $229 (), removed the drives and the fan, and replaced the drives with a pair of SSDs. That's not really very fast for Thunderbolt. Internal laptop hd (7200 rpm, sata): Write=42.99 Mb/sec, Read=38.09 Mb/secĮxternal G-Raid (esata): Write=134.76 Mb/sec, Read=192.32 Mb/secĮxternal Seagate hd (laptop drive, USB-2): Write=33.59 Mb/sec, Read=36.38 Mb/secĮxternal G-Raid (Firewire 800): Write=60.79 Mb/sec, Read=66.17 Mb/secĮncrypted sparsebundle image on external G-Raid above (esata): Write=68.66 Mb/sec, Read=81.33 Mb/sec Here's what I get using this method (and dividing by 1048576 to get Mb/sec): This one-liner will test the write speed, clear the cache, properly test the read speed, and then remove tstfile to reclaim disk space:ĭd if=/dev/zero bs=1024k of=tstfile count=1024 & purge & dd if=tstfile bs=1024k of=/dev/null count=1024 & rm tstfile The proper way to do the read test is to be to dd the tstfile created by the write benchmark into /dev/null (but only after clearing the RAM cache by using the 'purge' command). Using /dev/zero as dd's input and output file doesn't hit the disk at all and will return ridiculous speeds like 15-20 GB/sec. The read speed test is flawed as written.
#Macbook pro menumeters safe mac os x
Mac OS X Hints editor - Macworld senior contributor
0 kommentar(er)
