Coding for solid state drives

[Walter Bright via Digitalmars-d]

On 4/24/2015 2:18 AM, tcak wrote:
> On Friday, 24 April 2015 at 08:27:06 UTC, Walter Bright wrote:
>> http://codecapsule.com/2014/02/12/coding-for-ssds-part-6-a-summary-what-every-programmer-should-know-about-solid-state-drives/
>>
>>
>> An interesting article. Anyone want to see if there are any modifications we
>> should make to std.stdio to work better with SSDs? (Such as changing the
>> buffer sizes.)
>
>
> This article is not about "coding", but information about SSDs.

The section I linked to is definitely about coding for SSDs.


> Considering spinning drives and SSDs separately means create two separate
> configurations for software. So you either:
>
> 1. Provide two separate code one is written for one configuration, and another
> for SSD. This way the performance can be kept high,
>
> 2. Configurations can be changed on run-time, so there will be one executable
> only. But values won't be constant, so there is no compile time determination of
> values (buffer size etc.)
>
>
> For most end user, 2nd is suitable.

Things are configurable in std.stdio. But most people will just use the default 
settings. The default settings should be optimized for SSDs, not spinning drives.