Tag Info

Hot answers tagged


MB/s states how many Megabytes per second the drive can handle as throughput. IOPS states how many single operations per seconds can be handled. Sequential access means that for example one big file is read, random access means you're reading single parts of different files. If you look for a drive for database usage, you should look for: An ...


Generically, Megabytes/second are a metric for drive throughput, while IOPS represent I/O operations-per-second, a way of detailing the random I/O performance of the drive. Both measurements, as presented by manufacturers are fraught with inaccuracies. Throughput will be limited by SATA/SAS topology, the disk backplane (if present) and the RAID or storage ...


Boot with a maintenance CD that supports LVM, for example SystemRescueCD. Open a root shell. Reduce the size of /home: lvreduce --resizefs --size -150G /dev/mapper/vg_testsyst-lv_home The --resizefs option is essential, to reduce the size of the file system before you reduce the size of the volume that holds it. I believe that that option should work ...


Differences are: Intended market/usage. Enterprise drives are meant to be on 24/7 and can usually withstand higher temperatures or other stresses. Consumer grade drives are expected to be on 8-10 hours a day or so. Lifespan and MTBF are based off these expectations. Features included/supported by firmware. Enterprise drives may have more intelligent ...


Open a ticket- this is an indication that there's a lack of system memory, and if there's little work being done and you still had boxes go unresponsive, there's something screwy happening. I've walked through the process of inspecting internal memory usage before with support on the line, but it's not something clients are supposed to do on their own. You'd ...


Always on would let you have separate storage for each node. (http://msdn.microsoft.com/en-us/library/ff877884(v=sql.110).aspx) However this gets trickier in win10 with the new storage HA features.


Because drupal relies heavily on file_exists statements which can not be cached in APC and causes glusterfs to check with the quorum of servers to see if the file exists. So crazy horrible performance.

Only top voted, non community-wiki answers of a minimum length are eligible