![]() OS X is fully dedicated to run Virtualbox, and this box is the only box running on this system. As it really shouldn't lack speed with a Quad Core i7, 16GB RAM and a Samsung EVO 500GB drive. I thought enabling TRIM could be THE answer to this. I am searching for an answer on how my CentOS is lacking speed. It doensn't matter when I try to run this test, or how many times I run Sorry about the somewhat misleading title. If benchmarks run inside VM are misleading, how do I measure / benchmark the right way?Īn outcome of 15x higher speed (on first tests inside CentOS) is a big difference. Apr 2012, 11:53 Primary OS: Mac OS X other VBox Version: OSE Debian Guest OSses: CentOS 6.8 and 7.0 Partition 1 does not end on cylinder boundary. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes dev/sda: x86 boot sector GRand Unified Bootloader, stage1 version 0x3, boot drive 0x80, 1st sector stage2 0x849fc, GRUB version 0.94 partition 1: ID=0x83, active, starthead 32, startsector 2048, 1024000 sectors partition 2: ID=0x8e, starthead 221, startsector 1026048, 208689152 sectors, code offset 0x48ĭisk /dev/sda: 107.4 GB, 107374182400 bytesĢ55 heads, 63 sectors/track, 13054 cylinders I do know that it's not the SSD itself, but it's inside the virtual machine. ![]() The disk with the issues is "thiscouldbe 20160628-disk1.vdi" I attached the log file that you were asking for. The problem is that I haven't got a clue where to look. ![]() Timing buffered disk reads: 1134 MB in 3.00 seconds = 377.48 MB/secīut why? How come? Why is this older box slower until I repeat the test many times? ericovk Posts: 8 Joined: 4. The new CentOS 7 box gives me instant disk speed: (Mind the difference between /dev/sda and /dev/sda1) Timing buffered disk reads: 500 MB in 1.27 seconds = 393.30 MB/sec Timing buffered disk reads: 500 MB in 1.26 seconds = 396.04 hdparm -t /dev/sda1 Timing buffered disk reads: 500 MB in 1.24 seconds = 403.46 hdparm -t /dev/sda1 Timing buffered disk reads: 766 MB in 3.01 seconds = 254.36 hdparm -t /dev/sda1 Timing buffered disk reads: 696 MB in 3.02 seconds = 230.44 hdparm -t /dev/sda Timing buffered disk reads: 632 MB in 3.01 seconds = 210.00 hdparm -t /dev/sda Timing buffered disk reads: 258 MB in 3.00 seconds = 85.91 hdparm -t /dev/sda I don't understand the outcome of these tests as they vary a hdparm -t /dev/sda My older box is a CentOS 6.8 / Apache / PHP-FPM / with variable disk size. The biggest different is that I created a 10 GB fixed hdd size. Today I installed a new server next to my current box. Thanks but I am getting 500MB/s speeds on a new box I installed today when I repeat the benchmark a couple of times. I am running on a Mac Mini Server with SATA3 support. R/W multiple sector transfer: Max = 128 Current = 128ĭMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6Ĭycle time: no flow control=120ns IORDY flow control=120nsĪnyone knows what's wrong with my settings? Standby timer values: spec'd by Vendor, no device specific minimum Used: ATA/ATAPI-6 published, ANSI INCITS 361-2002ĬHS current addressable sectors: 16514064 In both CentOS and OS X, it isn't possible anymore to enable TRIM support.Ĭode: Select all Expand view Collapse view # hdparm -I /dev/sda (different tests show disk speeds of 500Mb/s read, 350MB/s write and 165 MB/s rewrite). It's still not the 500MB/s that speed test I am getting in Mac OS El Capitan with Disk Sensei. Hdparm -t /dev/sda1 gave me speeds aroubd 30MB/sĪfter enabling "Use Host IO cache" speeds are getting better at ± 250~350 MB/s. ![]() I was having speed trouble on CentOS & my Samsung EVO 500GB SSD drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |