|
|
![]() |
#1 | |
Sklee
|
![]() Quote:
MCS
__________________
Pillsbury, Minneapolis, Prince, Spoon Bridge and Cherry, coinkydink? |
|
![]() |
![]() |
![]() |
#2 |
1:11
![]() |
![]()
I guess my only question would be "why?"
I mean I like grape jelly, and I also like sushi, but you wont see me mixing the 2 together. ![]()
__________________
Cigar Asylum: A cigar board birthed without agendas, without profiting, and without advertisements. Amor puro Character is what you do when no one is watching |
![]() |
![]() |
![]() |
#3 |
Go Browns!
|
![]()
you are missing out my friend!!
__________________
diamonds/guns |
![]() |
![]() |
![]() |
#5 | |
Still Watching My Back
|
![]() Quote:
And you shouldn't be comparing them with SAS drives since those are really designed for different purposes. SAS are designed for high speed random access (especially random writes). Flash based SSD drive's random writes are pretty anemic compared to SAS drives (yes, sequential read/writes rock, but servers generally don't do a lot of sequential read/writes). Now DRAM based SSD would be great, but those have other drawbacks (namely if the power to the drives go down and you've not committed the transaction to some sort of non-volatile store, you're going to lose those transactions--a drawback, that's absolutely verboten in the server world). A hybrid DRAM based SSD with battery backup + harddrives would be great though, but also freakishly expensive, you know like the one that Sun recently introduced. Although I have no idea what would happen if a database engine wrote a transaction using write through mode--is that write hitting the DRAM or the harddrive? Anyways, kind of pointless diversion from the original topic. Which is a "cute but very impractical idea". |
|
![]() |
![]() |