搜索
首页数据库mysql教程数据库硬件选择

So you need to purchase a new database server, and you really don’t know where to start.. Because their maybe different recommendations for different OS’s I am going to stick with Linux with these recommendations. I want to say right off

So you need to purchase a new database server, and you really don’t know where to start..

Because their maybe different recommendations for different OS’s I am going to stick with Linux with these recommendations.  I want to say right off the bat here… choosing the right hardware should probably not be a five minute task.  I think you really need to spend time reviewing your application, it’s access patterns, the io capacity, etc.  You just can’t do this in five minutes generally.  But if your under the gun and asked me to spec something out today… here are some general guidelines.

As of  March 10th 2009 here is what I would recommend ( This are going to change every few months potentially with new versions of MySQL & new hardware:

CPU:
Currently the scalability of Innodb beyond 8 cores is limited, in fact with the current ( unpatched ) releases you may see a performance regression with more then 8 cores.  We wrote about this before.  If you have the money go with the fastest CPU’s available.  Avoid servers with lots of cores and a lower speeds.

Memory:
The more memory generally the better.  Here I would shoot for an amount of memory that will allow 100% of your hot data to be in memory.  If you do not know how much data is going to be hot, a good guess in my experience is 10-20% of the total database size , but that’s going to vary from application to application.   If you can’t figure out the total host data, more is better or a 20% rule of thumb is better then nothing.  Minimally plan for 2-4GB of memory to be allocated to the OS.  Typically I want at least 4GB of memory for the OS, and if I have a really active database I want more ( 8GB+ ).  When I say 4GB for the OS, this will also be used for the MySQL Per thread buffers/thread stack, etc.  So if you have a 24GB Database and all 24GB is hot or going to be used frequently I may put in 32GB of memory in my system and allocate 24GB to innodb and reserve the other 8GB for the OS and other items.

Disk:
Disk is going to be a toughy in 5 minutes.  You really have two concerns here, Disk capacity & IO Capacity (think io’s per second).  Disk capacity is generally pretty easy, I need XGB of disk space…  most people can estimate this no problems.   Keep in mind with RAID you will lose some raw disk capacity ( I.e. 4 160GB drives in a RAID 10 setup will deliver ~320GB of usable space ).    A 5 minute answer to IO capacity is a bit more of a challenge.    One of the descisions  yo will need to make if you can get by with internal disk or you need a SAN.  Just the other day Peter Z wrote about when to choose a SAN…  give it a read.  Assuming your making a decision in 5 mintes I am going to make an assumption that your going to look for internal disk.   Purchasing the correct SAN in my opinion requires a lot of thought.   So Let assume you want to use internal disk. First If all of your data fits into memory, it lessons your disk requirements a bit but it will not eliminate disk IO   ( your still going to read and write to disk, but your reads should be lessened ).  I strongly urge that you keep the database and OS completely separate.   So that’s 2 disks for the OS ( mirrored disks should be fine ).  For the database I typically recommend RAID10 for the data ( RAID 5 maybe OK for database with fewer writes, I.e.  data warehouses )  which means a minimum of 4 disks for your database.  So thats 6 disks to start with.  You can then scale up from there  as you need more, without more analysis your going to be guessing here.     In terms of the type of drives, SAS or SCSI in either 10K or 15K speeds are pretty standard.  I would avoid SATA drives that are

Disk Controller:
Cache on your disk controller is important and the more the better in most cases. Make sure your controller has a battery backup, otherwise its really useless.

Network Cards:

Purchase at least two network cards for your system, both full 1GBE. Typically I would bond these two nics together to give some redundancy.  Also avoid dropping your new server into a 100Mb/s network as well.

A quick note on the OS… make sure you install a 64 bit OS!

原文:http://www.bigdbahead.com/?p=158

声明
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系admin@php.cn
解释酸的特性(原子,一致性,隔离,耐用性)。解释酸的特性(原子,一致性,隔离,耐用性)。Apr 16, 2025 am 12:20 AM

ACID属性包括原子性、一致性、隔离性和持久性,是数据库设计的基石。1.原子性确保事务要么完全成功,要么完全失败。2.一致性保证数据库在事务前后保持一致状态。3.隔离性确保事务之间互不干扰。4.持久性确保事务提交后数据永久保存。

MySQL:数据库管理系统与编程语言MySQL:数据库管理系统与编程语言Apr 16, 2025 am 12:19 AM

MySQL既是数据库管理系统(DBMS),也与编程语言紧密相关。1)作为DBMS,MySQL用于存储、组织和检索数据,优化索引可提高查询性能。2)通过SQL与编程语言结合,嵌入在如Python中,使用ORM工具如SQLAlchemy可简化操作。3)性能优化包括索引、查询、缓存、分库分表和事务管理。

mySQL:使用SQL命令管理数据mySQL:使用SQL命令管理数据Apr 16, 2025 am 12:19 AM

MySQL使用SQL命令管理数据。1.基本命令包括SELECT、INSERT、UPDATE和DELETE。2.高级用法涉及JOIN、子查询和聚合函数。3.常见错误有语法、逻辑和性能问题。4.优化技巧包括使用索引、避免SELECT*和使用LIMIT。

MySQL的目的:有效存储和管理数据MySQL的目的:有效存储和管理数据Apr 16, 2025 am 12:16 AM

MySQL是一种高效的关系型数据库管理系统,适用于存储和管理数据。其优势包括高性能查询、灵活的事务处理和丰富的数据类型。实际应用中,MySQL常用于电商平台、社交网络和内容管理系统,但需注意性能优化、数据安全和扩展性。

SQL和MySQL:了解关系SQL和MySQL:了解关系Apr 16, 2025 am 12:14 AM

SQL和MySQL的关系是标准语言与具体实现的关系。1.SQL是用于管理和操作关系数据库的标准语言,允许进行数据的增、删、改、查。2.MySQL是一个具体的数据库管理系统,使用SQL作为其操作语言,并提供高效的数据存储和管理。

说明InnoDB重做日志和撤消日志的作用。说明InnoDB重做日志和撤消日志的作用。Apr 15, 2025 am 12:16 AM

InnoDB使用redologs和undologs确保数据一致性和可靠性。1.redologs记录数据页修改,确保崩溃恢复和事务持久性。2.undologs记录数据原始值,支持事务回滚和MVCC。

在解释输出(类型,键,行,额外)中要查找的关键指标是什么?在解释输出(类型,键,行,额外)中要查找的关键指标是什么?Apr 15, 2025 am 12:15 AM

EXPLAIN命令的关键指标包括type、key、rows和Extra。1)type反映查询的访问类型,值越高效率越高,如const优于ALL。2)key显示使用的索引,NULL表示无索引。3)rows预估扫描行数,影响查询性能。4)Extra提供额外信息,如Usingfilesort提示需要优化。

在解释中使用临时状态以及如何避免它是什么?在解释中使用临时状态以及如何避免它是什么?Apr 15, 2025 am 12:14 AM

Usingtemporary在MySQL查询中表示需要创建临时表,常见于使用DISTINCT、GROUPBY或非索引列的ORDERBY。可以通过优化索引和重写查询避免其出现,提升查询性能。具体来说,Usingtemporary出现在EXPLAIN输出中时,意味着MySQL需要创建临时表来处理查询。这通常发生在以下情况:1)使用DISTINCT或GROUPBY时进行去重或分组;2)ORDERBY包含非索引列时进行排序;3)使用复杂的子查询或联接操作。优化方法包括:1)为ORDERBY和GROUPB

See all articles

热AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover

AI Clothes Remover

用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool

Undress AI Tool

免费脱衣服图片

Clothoff.io

Clothoff.io

AI脱衣机

AI Hentai Generator

AI Hentai Generator

免费生成ai无尽的。

热门文章

R.E.P.O.能量晶体解释及其做什么(黄色晶体)
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.最佳图形设置
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.如果您听不到任何人,如何修复音频
4 周前By尊渡假赌尊渡假赌尊渡假赌
R.E.P.O.聊天命令以及如何使用它们
4 周前By尊渡假赌尊渡假赌尊渡假赌

热工具

ZendStudio 13.5.1 Mac

ZendStudio 13.5.1 Mac

功能强大的PHP集成开发环境

PhpStorm Mac 版本

PhpStorm Mac 版本

最新(2018.2.1 )专业的PHP集成开发工具

Dreamweaver CS6

Dreamweaver CS6

视觉化网页开发工具

VSCode Windows 64位 下载

VSCode Windows 64位 下载

微软推出的免费、功能强大的一款IDE编辑器

Dreamweaver Mac版

Dreamweaver Mac版

视觉化网页开发工具