Virtual machines and SSD: as safer and faster?

Today I moved the system on the SSD, like there is still a place to throw it on a VMWare virtual machine. Much thought — how will this affect the health of the disk? Two cars for about 20 gigs. Alternatives — to keep them on:
• SATA II HDD 1.5 TB WD15EURS (obviously so-so option)
• each stripe of the two Samsung HD502HI
I advise the respected community? How the file may be harmful to SSD? Will there be a significant increase in speed or is it better to keep on the other screw?
October 3rd 19 at 03:07
5 answers
October 3rd 19 at 03:09
The same harmful as any other use of the disk, you bought to look after him?
Well, the die will change under warranty and quickly deployed with backup.
In General, this I came to the end. - Onie_Runte commented on October 3rd 19 at 03:12
Because, damn it, under warranty-they don't die. A week after — please =) - alice_Swaniawski commented on October 3rd 19 at 03:15
Well after 5 years buy a new one as if you buy them a million pieces right the splurge. - Bella.Witting commented on October 3rd 19 at 03:18
Exactly. If VM are no pitfalls when you work on the SSD — the problem is solved. Even if not in 5, and after 2 years, it will still be acceptable. - Onie_Runte commented on October 3rd 19 at 03:21
October 3rd 19 at 03:11
why buy a ssd and not use it? Itself dev ain't gonna do ssd, and the operating system you can just readjust if you wish. And Yes, the increase is (I have two path raised, both on debian, one on ssd and another on hdd. The difference is palpable),
Thanks, Yes, the axle is already configured. Response to the Treasury put. - Onie_Runte commented on October 3rd 19 at 03:14
October 3rd 19 at 03:13
Barely in the settings of the path included caching of record, the disk accesses will be reduced to a minimum. And read the gain will be for sure.
Oh, but about the write cache in virtual reality and I forgot, thank you! - Onie_Runte commented on October 3rd 19 at 03:16
October 3rd 19 at 03:15
If you're talking about SSD wear, it
depending on TRIM support
and
depending on how much RAM you have
and
— the minimum free space that will remain on the SSD when filling your virtual machines, keeping them snapshots, States, etc. If you stay less than 30% — it's better not,
and
— availability of UPS.

If RAM is small(4 or less), then the SSD is better to place swap of the system, which by the way will sopitsa and virtual machines. If a lot of RAM (12+), the entire cache can fit in it, and the SSD is great — then you can place frequently used files. However, I would suggest this configuration:
— SSD under system
mirror two Samsung for all your projects and important data. here the virtual machine. not a stripe because stripes is very easy and sadly lost the information.
— the third disk of 1.5 TB under non-critical data (backups, distros, movies, music)
It is based on the fact that the screw is cheaper to buy new than to repair information from the experts, and that the screws are dying suddenly, and that SSD perceive critical power fails.
Of RAM 24 gig. With the rest about it is, the slower the screw under backup on the stripe work. But the SSD is small, but still it is still 30 gigs of free space left. Intel SSD 530 series 180 gigs. - Onie_Runte commented on October 3rd 19 at 03:18
Yes, the stripe and the system will be daily backuptest. And UPS is. I can direct a gentleman feel :) - alice_Swaniawski commented on October 3rd 19 at 03:21
That is, you have a system is 150 gigs? And where many, if not a secret?
In any case, even the free 30 of 180 is not enough. If you continue to fill — will greatly increase the wear. Read about the technology wear leveling.
The stripe is not needed, make the mirror, say thank you when one of the Samsung models will be covered. Although this is oftop. - Bella.Witting commented on October 3rd 19 at 03:24
Fill not going, is already the upper limit, I think. 150 gigs is a graphical machine. Software for graphics and video. For wear leveling thanks, was not aware of, I will vkurivat. - Onie_Runte commented on October 3rd 19 at 03:27
With such filling of the answer is to store the virtual machine on SSD is not recommended. - Onie_Runte commented on October 3rd 19 at 03:30
Moor
By the way, the performance of NTFS on the HDD very good effect Diskeeper. - Onie_Runte commented on October 3rd 19 at 03:33
With such filling of the answer is to store the virtual machine on SSD is not recommended.

Yes I also think that it is not quite right. But more briskly fly. And in virtualcad particularly to grow nothing — they are used only for each specific software. I will try, probably for some time to drive to the SSD, will look what will happen. - Onie_Runte commented on October 3rd 19 at 03:36
Work with a filled SSD turns slower read or write, and the uneven wear of the cells. - Onie_Runte commented on October 3rd 19 at 03:39
Screw size is 180 GB, how much do you think it's right to keep free space? - alice_Swaniawski commented on October 3rd 19 at 03:42
Moor
I'd like this example shows. Imagine that the SSD consists of 65535 cells (from address 0x0001..0xFFFF) is empty, and you're writing the first block. It will be recorded in the logical address 0x0001. Physically, it will also comply with the cell 0х0001. Then you overwrite the block with the modified data. At this point, the controller remaps the logical block 0x0001 0x0002 cell. The next rewrite it will be the cell 0x0003 and so on. Thus, despite the fact that one cell can withstand only 5 thousand cycles of rewriting, you can rewrite the 5000 block*65535 times. That is, the probability of the first failure of the cell after approximately 327 million times recording. This despite the fact that you are recording one block and the other blocks are occupied.
The controller may reassign blocks only in free cells. And if 90% of cells are occupied, the alternate recording will be only the remaining 10%. And it is correspondingly, 10 times less. And the first failure of cells will happen 10 times faster. But if the busy 99% of the disk 100 times faster.
The reasoning is understandable? This is wear leveling.
That is, according to rough estimates, ssd, half-filled, half will live longer than 3/4 filled and five times longer than the completed on 9/10. And for each subsequent employed megabytes "price" use is growing faster and faster.

Manufacturers offer a guarantee of three years, focusing on the volume of records (20 GB per day) and free space on the disk the average user. I think it's 20 percent. - Onie_Runte commented on October 3rd 19 at 03:45
Very nice explained, thank you. Now I can easily see all 37 GB of 180, the situation is changing only during the inclusion of virtuallock, biting another 8 gigs on time. So I kind of support the normal working conditions. - alice_Swaniawski commented on October 3rd 19 at 03:48
October 3rd 19 at 03:17
It all depends on the nature of the work virtual machine, namely the ratio R/W.
For example VDI infrastructure — many think that installing an SSD will give a significant increase in VDI, the ratio r/w 30/70 — f gj-write speed of the SSD is not so much better than a good RAID, but in terms of reliability and yields.
In mind those requirements that You have, I would suggest using a combined approach — the stripe under the data ssd swap partition
I understand You correctly − the system to supply 1.5 TB screw from 5400 rpm to swapits on the SSD and keep the data in the stripe? I think for me it would be the least logical solution. I use virtual machines (one with Macau, the other with Win7) once a week for a few hours, each of them actually only use the minimum necessary application. - Onie_Runte commented on October 3rd 19 at 03:20
2 put in the mirror, 1 for swap and temp virtuallock and guest OS.
My work whom it is done so (only under system raid 10 made) + 64Gb ssd — temp + swap.
If you use a SSD for the system it is not very long to live. Think that will save a backup there as usual at the right time it will not.
And so the volume is decent, and redundancy drives increase system performance and application in General, no matter how cool. - alice_Swaniawski commented on October 3rd 19 at 03:23
> If you use a SSD for the system it is not very long to live.

First, it is doubtful, and secondly, under the system it makes sense to put. The whole system becomes more agile. And you can combine with swap. - Bella.Witting commented on October 3rd 19 at 03:26
I think I will support it. For me the main thing — the performance. Until yesterday all this machinery was standing on only one 1.5 TB 5400 broken to the partition. I can't describe in words how fast compared to previous version all works now. Even if SSD will live a year and a half that's fine with me, daily backups Acronis'ω, sector-by-sector image of the system plus the file stripe. - Onie_Runte commented on October 3rd 19 at 03:29
And the swap I have yet to experiment at all removed. Still, 24 gig memory — not so little, promontory like that without swap will work. - Onie_Runte commented on October 3rd 19 at 03:32

Find more questions by tags Virtual machineVMware