how_to:performance_requirements
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revisionLast revisionBoth sides next revision | ||
| how_to:performance_requirements [2012/04/13 10:21] – created paul | how_to:performance_requirements [2016/09/29 16:48] – [High Requirements] paul | ||
|---|---|---|---|
| Line 25: | Line 25: | ||
| SSDs (Solid State Devices) are capable of much more , typically over 5000 IOPS, even up to 250,000 IOPS. | SSDs (Solid State Devices) are capable of much more , typically over 5000 IOPS, even up to 250,000 IOPS. | ||
| - | As an example, one of our VPOP3 hosted service servers was running with a RAID 10 array on SATA drives, with no BBWC. This hit performance issues, the IOPS was around 170 IOPS, and the Avg Disk Queue was regularly over 3 or 4 for long periods of time. We moved this to a new server with a RAID 10 array on 15000 SAS drives with a BBWC, the IOPS has increased slightly to 230 IOPS, but the Avg Disk Queue is now about 0.2, and the performance is much greater. | + | As an example, one of our VPOP3 hosted service servers was running with a RAID 10 array on SATA drives, with no BBWC. This encountered |
| If the Avg Disk Queue is high, but the IOPS is not too high for the disks, then the issue may be disk fragmentation. If the disk is highly fragmented, then the disk subsystem will take longer than normal to process requests, so defragmenting the disk is a good thing to try. | If the Avg Disk Queue is high, but the IOPS is not too high for the disks, then the issue may be disk fragmentation. If the disk is highly fragmented, then the disk subsystem will take longer than normal to process requests, so defragmenting the disk is a good thing to try. | ||
| + | |||
| + | **Never use RAID 5 for any database server - such as VPOP3 uses - RAID 5 will be very slow when many small updates are made, such as to database tables** | ||
| =====Examples===== | =====Examples===== | ||
| ====Low Requirements==== | ====Low Requirements==== | ||
| - | For example, | + | For example, |
| * Dual core 2.4 GHz Core2Duo or better | * Dual core 2.4 GHz Core2Duo or better | ||
| - | * Windows XP or Windows 7 or better | + | * Windows 7 or better |
| * 4 GB RAM or more | * 4 GB RAM or more | ||
| * 7200RPM SATA drives | * 7200RPM SATA drives | ||
| ====High Requirements==== | ====High Requirements==== | ||
| - | For example, | + | For example, |
| * Quad core 2.6GHz Xeon or better | * Quad core 2.6GHz Xeon or better | ||
| - | * Windows | + | * Windows 2008 or 2012 R2 server |
| * 8 GB RAM or more | * 8 GB RAM or more | ||
| - | * Hardware RAID controller with BBWC (Battery Backed Write Cache) and 128MB or more cache RAM | + | * Hardware RAID controller with BBWC (Battery Backed Write Cache) and 512MB or more cache RAM |
| * 15000 RPM SAS (Serial Attached SCSI) drives in a RAID 1 or RAID 10 configuration | * 15000 RPM SAS (Serial Attached SCSI) drives in a RAID 1 or RAID 10 configuration | ||
| Line 55: | Line 57: | ||
| Using separate partitions on the same physical disk will slow things down, rather than speed them up, so that is not recommended. | Using separate partitions on the same physical disk will slow things down, rather than speed them up, so that is not recommended. | ||
| - | This is an advanced option which we can help with on an individual level | + | Here are [[v5_-_move_the_message_store_to_a_new_folder_drive|instructions |
how_to/performance_requirements.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1
Page Tools
