I used CrystalDiskMark to test the writing speed of my SSD, it is almost 6GB per second, so I had thought this work should not be that hard. I do know from experience I can destroy an HDD in a matter of months quite reliably by this method if implemented naively. Now I get about 3.6GB data per second in memory, and I need to write them on my SSD continuously. When the write speed is low the RAM fills up with images and the total number of images that I can acquire in a given time is greatly reduced. I've done something not too different from this for months-not-years without adverse effects, but that was years ago, and I haven't done serious testing. My problem is that, while monitoring the usage of the SSD in the Task Manager, that the write speed to the SSD can fluctuate between 200 MB/sec and 10 MB/sec even though the usage is 100. Does my many-small-writes application put my SSD on the way to destruction? Would I be safer if I cached to memory and wrote to disk in chunks every minute/hour? Obviously this is more complicated (web service to the memory cache for the most recent minute/hour, disk for older data), but I also prefer not to destroy too much hardware. Machine type, Maximum write IOPS, Maximum read IOPS, Maximum write throughput. ![]() I do vaguely understand SSDs are made out of cells which have to be updated on an all-or-none basis, and also that each cell can withstand only so many writes (hundreds or thousands, I think, for commodity drives). With the same maximum IOPS as SSD persistent disks and lower IOPS per GB. Is it safe for the SSD if I perform several hundred ~50 byte file-append writes per second? I suspect the OS might aggregate these writes, but I don't know. ![]() I want to cache these to an SSD for further processing. It is measured in IOPS (Input/Output Operations Per Second) and is a good indication. I have an application which receives several hundred strings per second, about fifty bytes long, over the network. This is the maximum random write speed according to the manufacturer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |