|
![]() |
|
| Author |
|
|||||||
|
jmr
Posts: 6127
Location: Brisbane, Queensland
|
Sup yall
Gotta build a dev server - and I am evaluating HDD's. Will be used for some DB work, potentially running 2 VM's. ATM I am weighing up the HDD options (Gotta be 1RU so RAID-1). 147GB SAS Drives and 120GB SSD Drives are virtually the same price, but I thought I would check a few peoples opinions on their reliability in an enterprise environment (taking MTBF with salt) |
|||||||
| #0 11:14am 15/12/08 |
|
|||||||
|
system
|
--
|
|||||||
| #0 |
|
|||||||
|
DecayingCorpse
Posts: 1614
Location: Brisbane, Queensland
|
go sas.
nothing like em. |
|||||||
| #1 11:19am 15/12/08 |
|
|||||||
|
tequila
Posts: 437
Location: Brisbane, Queensland
|
imo get 10krpm+ 2.5" sas drives
solid state isn't that s*** hot yet, we're only using it for an experimental thing which involves *a lot* of i/o also you can now get 300gb 2.5" drives from hp |
|||||||
| #2 11:22am 15/12/08 |
|
|||||||
|
Raven
Posts: 3164
Location: Melbourne, Victoria
|
SSD on a database if you want the disk to die (or shrink the amount of usable space) within a few months. Unless you're doing basically only reads, go SAS.
|
|||||||
| #3 11:37am 15/12/08 |
|
|||||||
|
Jim
Posts: 8967
Location: Brisbane, Queensland
|
and don't use vm's unless you're putting vmware on bare metal, you'll probably be very disappointed by the i/o
|
|||||||
| #4 01:24pm 15/12/08 |
|
|||||||
|
Pinky
Posts: 171
Location: Melbourne, Victoria
|
What do you mean by 'bare metal'? I use VMs for testing software releases for OSs that I don't want to install. Plus using a VM for linux is better than say installing MinGW under Windows just so you can use a decent GCC/Code::Blocks dev env. Especially on Vista. |
|||||||
| #5 01:28pm 15/12/08 |
|
|||||||
|
Nailbomb
Posts: 2599
Location: Melbourne, Victoria
|
What do you mean by 'bare metal'? I assume he means an ESX server. |
|||||||
| #6 01:29pm 15/12/08 |
|
|||||||
|
trog
AGN Admin
Posts: 25645
Location: Brisbane, Queensland
|
SSD on a database if you want the disk to die (or shrink the amount of usable space) within a few months. Unless you're doing basically only reads, go SAS.Rly? Some of the blogs I read about mysql, some of the guys have switched to using SSDs and are superstoked with them from a performance level. This is fairly recent tho and I haven't read any posts about failures yet, but I'm keeping an eye out to see how they go. Here's one post from one of the blogs - the performance increase is crazy. here's another - writes are, as you suggest, pretty average though. |
|||||||
| #7 01:36pm 15/12/08 |
|
|||||||
|
Jim
Posts: 8970
Location: Brisbane, Queensland
|
What do you mean by 'bare metal'? yeah and even then I have no idea how it performs because I haven't tried it. surely it's a lot better though all I know is that vmare server installed into windows and linux seems to suck at i/o. we've tried using it extensively for dev environments and even when a vm has a dedicated host, it's performance is abundantly worse than the exact same dev environment installed into the host directly. to the point where we've now ditched it in that context even though it means we lose the portability and ease of restore when the host fails. this is on enterprise-grade hardware with decent disks/controllers with plenty of battery-backed cache. I use VMs for testing software releases for OSs that I don't want to install.sure, but that may not be what jmr was talking about when he said 'dev server', especially given that he talked about databases as well. |
|||||||
| #8 01:45pm 15/12/08 |
|
|||||||
|
Raven
Posts: 3166
Location: Melbourne, Victoria
|
Rly? Some of the blogs I read about mysql, some of the guys have switched to using SSDs and are superstoked with them from a performance level. This is fairly recent tho and I haven't read any posts about failures yet, but I'm keeping an eye out to see how they go. Here's one post from one of the blogs - the performance increase is crazy. here's another - writes are, as you suggest, pretty average though. I don't debate at all that they're bloody quick - they are. I just question the integrity of any data that's stored on a device where you're doing frequent over-writes, and each block has a limited re-use life. |
|||||||
| #9 01:50pm 15/12/08 |
|
|||||||
|
Jim
Posts: 8972
Location: Brisbane, Queensland
|
it depends on what 'limited' means
traditional hard disks will eventually be unable to read/write from/to their platters due to wear and tear, so why do you not question the integrity of data stored on them? so really, the only question in that regard is: does the expected lifetime of the media fit in with your lifecycle management plans? also, it's entirely feasible that people are happy to change their plans in that regard simply due to the performance gains |
|||||||
| #10 01:58pm 15/12/08 |
|
|||||||
|
Opec
Posts: 5494
Location: Brisbane, Queensland
|
Go with SAS.
|
|||||||
| #11 02:43pm 15/12/08 |
|
|||||||
|
Scorp
Posts: 225
Location: Brisbane, Queensland
|
Nothing to even discuss here, SAS. Without a doubt. When SSD is ready for the server environment you'll know about it.
|
|||||||
| #12 05:49pm 15/12/08 |
|
|||||||
|
Gesthemene
Posts: 437
Location: Brisbane, Queensland
|
Another vote for SAS here.
Also, ESXi 3.5 isn't bad, particularly on HP servers. Set up a test server the other day for SBS08 within ESXi 3.5. Good price for it too ;) |
|||||||
| #13 06:27pm 15/12/08 |
|
|||||||
|
whoop
Posts: 13201
Location: Brisbane, Queensland
|
||||||||
| #14 08:19pm 15/12/08 |
|
|||||||
|
Jim
Posts: 8977
Location: Brisbane, Queensland
|
When SSD is ready for the server environment you'll know about it.I think you missed the boat dude ssd is being deployed, has been for months. it's absolutely ready, unless you're implying it's cost renders it unready |
|||||||
| #15 11:03pm 15/12/08 |
|
|||||||
|
system
|
--
|
|||||||
| #15 |
|
|||||||
|
| ||||||||