Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
"Unfortunately, our today’s tests do not provide a clear answer to the question if building a RAID0 out of modern SSDs makes sense. This solution has its highs and lows and we can only do as much as lost them all and let you be the decision maker.
RAID0 is a traditional method of boosting your disk subsystem performance. The trick works with SSDs, too. Combining two SSDs into a RAID0 helps increase linear read/write speeds as well as the speed of processing small data blocks at a long request queue. We did notch very impressive sequential read and write speeds in our tests, getting much higher than the SATA 6 Gbit/s bandwidth.
However, we should keep it in mind that modern SSDs have a tendency to get faster as their capacity grows even within the same product series, so a two-disk RAID0 may turn out to be slower than a single large-capacity SSD. More importantly, SATA RAID controllers, including those in modern chipsets, do not support the TRIM command. As a result, the array’s writing performance degrades over time whereas single SSDs are less susceptible to this problem.
Thus, a RAID0 will only be superior to a single SSD at linear operations whereas random-address operations will expose its weakness. That’s why we can’t prefer the RAID0 solution to a single SSD without reservations. On the other hand, most of our lifelike benchmarks do show the RAID0 to be overall faster. In other words, the RAID0 is better on average, especially as it doesn’t involve any investment: the cost per gigabyte is the same for a RAID0 and an SSD of the same capacity.
There is some inconvenience about running an SSD RAID0 that should also be mentioned. You cannot monitor the health of your SSDs in a RAID0 or update their firmware. A RAID0 will also have lower reliability since a failure of any SSD causes the loss of all data stored on all the SSDs in the array."
Hope this answers your question.
Personaly, I prefer a 128GB SSD for my OS and a 3TB for everything else. I don't get the fastest loading, but it still loads after then just a HDD.
I have a 120GB SSD for OS, a 1TB HDD for programs (games), and a 2TB for media right now
The link I posted didn't say it wouldn't work, just that it isn't any faster, overall then one drive. Some parts may run faster while others may run slower. It balances out.
Remember, a traditional HDD needs to locate the data on the platter by moving a head to that area. A SSD doesn't have to search and read. It knows where the data is and can bring it up almost instantly.
A raid0 would have the HDDs search and transfer at the same time, There isn't much point in it with an SSD.
For example, on Linux if you add a RAID1 member with --write-mostly and --write-behind options, that drive will not serve read requests unless the other drive(s) (in this case SSDs) are busy, and will not block writes unless it's too far behind (configurable), so you get SSD read speed, close to SSD write speed, and protection in case of failure.
Some posts about this approach:
http://www.vinsec.net/2012/05/hybrid-hdd-ssd-raid1.html
http://tansi.info/hybrid/
Unfortunately I am not aware of any Windows RAID solutions having such options.
Also, most RAID solutions do not support TRIM, which may cause SSD performance to degrade (http://en.wikipedia.org/wiki/TRIM#RAID_issues). On Linux a proper TRIM support on RAID (without manually running a special tool) is available only since the recently released 3.7 kernel.