Great info to learn on determining IOPS required for Horde

By -

Determining disk drives if you know the IOPS required


If you can make an estimate of how many I/O's Per Second (IOPS) you need you can determine how many disks you'll need as RAID10 and how many disks you'll need as RAID5.
Generally, a single disk drive can do this many IOPS per disk:
15k rpm: 180-210 IOPS
10k rpm: 130-150 IOPS
7200 rpm: 80-100 IOPS
5400 rpm: 50-80 IOPS
In a mirrored configuration:
Disk IOPS = Read IOPS + (2 * Write IOPS)
In a parity (RAID5) configuration:
Disk IOPS = Read IOPS + (4 * Write IOPS)

Example calculations

Now let's look at an example. If you estimate that you need to support 40 Read IOPS (40 reads/sec) and 80 Write IOPS (80 writes/sec).
If you want to use a mirrored configuration of drives:
Disk IOPS = Read IOPS + (2 * Write IOPS) = 40r/s + (2 * 80w/s) = 200 Disk IOPSUsing 7200 rpm drives, you need: 200 / 50 = 4 disk drives
Using 10k rpm drives, you need: 200 / 130 = 2 disk drives (always round up)
If you want to use a parity (RAID5) configuration of drives:
Disk IOPS = Read IOPS + (4 * Write IOPS) = 40r/s + (4 * 80w/s) = 360 Disk IOPSUsing 7200 rpm drives, you need: 360 / 50 = 8 disk drives (always round up)
Using 10k rpm drives, you need: 360 / 130 = 3 disk drives


You can also refer to this page, http://www.pcguide.com/ref/hdd/op/spin_Speed.htm where you can benchmark your IOPS base on their expected latency.

ref. http://wiki.horde.org/HardwareRequirements

Comments

Post a Comment

Popular posts from this blog

Converting sectors into MB - Useful in understanding the sectors in iostat in Linux

By -
Supposed you have a sector with 512 Bytes equivalent, then the formula will be just below 1 sect. 1024 Bytes 1024 KB --------- x ---------- x --------- = 2048 sect./ MB 512 Bytes 1 KB 1 MB i.e. if a sector has a 512 Bytes, commonly in a hard disk, so which means that a 1024 Bytes == 2 sector of a KiloByte. So if 2 sector is equivalent to a KiloByte (1024 Bytes), if you do the math, 2 ** 1024 / 512.0 = 2048. This is useful only understanding the iostat process in Linux.
Read more

What is Disk Contention?

By -
Okay, so let me take a note about this meaning... Disk contention occurs when multiple processes try to access the same disk simultaneously. Most disks have limits on both the number of accesses (I/O operations each second) and the amount of data they can transfer each second (I/O data rate, or  throughput ). When these limits are reached, processes must wait to access the disk. It's a situation occurring when multiple processes try to access the same disk(s) and the requests outrun the response times of the drive(s). This happens because most disks are restricted in the amount of data they can transfer and the number of accesses (I/O operations) they can handle each second. Disk contention became a more prominent problem when CPU speeds dramatically increased over the past 15 years, putting even greater demands on disk-based data storage and causing the modern data centers’ most significant operational constraint.
Read more

Installing MySQL from source: Could NOT find Curses (missing: CURSES_LIBRARY CURSES_INCLUDE_PATH)

By -
Just find this a terrible problem with my CentOS having x86_64 architecture and cmake failed to find the right library for Curses. Anyway, this is how I got the error when trying to build MySQL from source , $ cmake . -- Running cmake version 2.6.4 -- MySQL 5.6.12 -- Packaging as: mysql-5.6.12-Linux-x86_64 -- HAVE_VISIBILITY_HIDDEN -- HAVE_VISIBILITY_HIDDEN -- HAVE_VISIBILITY_HIDDEN -- Could NOT find Curses  (missing:  CURSES_LIBRARY CURSES_INCLUDE_PATH) CMake Error at cmake/readline.cmake:85 (MESSAGE):   Curses library not found.  Please install appropriate package,       remove CMakeCache.txt and rerun cmake.On Debian/Ubuntu, package name is libncurses5-dev, on Redhat and derivates it is ncurses-devel. Call Stack (most recent call first):   cmake/readline.cmake:128 (FIND_CURSES)   cmake/readline.cmake:202 (MYSQL_USE_BUNDLED_EDITLINE)   CMakeLists.txt:332 (MYSQL_CHECK_EDITLINE) -- Configuring incomplete, errors occur...
Read more