Coding for solid state drives
Laeeth Isharc via Digitalmars-d
digitalmars-d at puremagic.com
Sat Apr 25 07:19:30 PDT 2015
On Saturday, 25 April 2015 at 11:34:22 UTC, ketmar wrote:
> On Fri, 24 Apr 2015 01:27:15 -0700, Walter Bright wrote:
>
>> if there are any
>> modifications we should make to std.stdio to work better with
>> SSDs?
>> (Such as changing the buffer sizes.)
>
> yes: don't do anything. it's OS task to cope with that.
well beyond the area I know, but it seems like given the relative
structure of costs for random seeks for SSDs you often want to
process files in parallel, whereas the opposite is true for
spinning platters. The OS can't help you here.
perhaps not for the standard library, but maybe it would be nice
to have a function to detect whether a path is on an SSD or not.
I am not sure if there is a standard way to detect this. There
is a hacker way here:
https://stackoverflow.com/questions/908188/is-there-any-way-of-detecting-if-a-drive-is-a-ssd
and some others check the output of smartmontools.
But surely, it would be a start to make it easy for the user to
know so she can shape her approach accordingly.
More information about the Digitalmars-d
mailing list