Re: Coding for solid state drives

2015-04-25 Thread Walter Bright via Digitalmars-d
On 4/25/2015 1:42 PM, Xinok wrote: On Saturday, 25 April 2015 at 20:12:55 UTC, Walter Bright wrote: Hard disks are dead today for anyone who cares about performance. I still use them, but only for secondary storage. For anybody who wants to buy 4TB of storage for $100, hard drives are still

Re: Coding for solid state drives

2015-04-25 Thread Walter Bright via Digitalmars-d
On 4/24/2015 10:24 PM, Vladimir Panteleev 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

Re: Coding for solid state drives

2015-04-25 Thread Xinok via Digitalmars-d
On Saturday, 25 April 2015 at 20:12:55 UTC, Walter Bright wrote: Hard disks are dead today for anyone who cares about performance. I still use them, but only for secondary storage. For anybody who wants to buy 4TB of storage for $100, hard drives are still very much alive. Not to mention

Re: Coding for solid state drives

2015-04-25 Thread Walter Bright via Digitalmars-d
On 4/24/2015 10:26 PM, Vladimir Panteleev wrote: On Friday, 24 April 2015 at 19:35:08 UTC, Walter Bright wrote: 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. That would be

Re: Coding for solid state drives

2015-04-25 Thread ketmar via Digitalmars-d
On Sat, 25 Apr 2015 16:40:51 +, Laeeth Isharc wrote: On Saturday, 25 April 2015 at 16:10:11 UTC, ketmar wrote: On Sat, 25 Apr 2015 14:19:30 +, Laeeth Isharc wrote: But surely, it would be a start to make it easy for the user to know so she can shape her approach accordingly. i

Re: Coding for solid state drives

2015-04-25 Thread ketmar via Digitalmars-d
On Sat, 25 Apr 2015 16:40:51 +, Laeeth Isharc wrote: On Saturday, 25 April 2015 at 16:10:11 UTC, ketmar wrote: On Sat, 25 Apr 2015 14:19:30 +, Laeeth Isharc wrote: But surely, it would be a start to make it easy for the user to know so she can shape her approach accordingly. i

Re: Coding for solid state drives

2015-04-25 Thread ketmar via Digitalmars-d
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. signature.asc Description: PGP signature

Re: Coding for solid state drives

2015-04-25 Thread Laeeth Isharc via Digitalmars-d
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

Re: Coding for solid state drives

2015-04-25 Thread ketmar via Digitalmars-d
On Sat, 25 Apr 2015 14:19:30 +, Laeeth Isharc wrote: But surely, it would be a start to make it easy for the user to know so she can shape her approach accordingly. i believe that this must be controlled with `version` or cli arg, and it belongs to application logic, not standard library.

Re: Coding for solid state drives

2015-04-25 Thread Vladimir Panteleev via Digitalmars-d
On Saturday, 25 April 2015 at 14:19:31 UTC, Laeeth Isharc wrote: 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

Re: Coding for solid state drives

2015-04-25 Thread Laeeth Isharc via Digitalmars-d
On Saturday, 25 April 2015 at 16:10:11 UTC, ketmar wrote: On Sat, 25 Apr 2015 14:19:30 +, Laeeth Isharc wrote: But surely, it would be a start to make it easy for the user to know so she can shape her approach accordingly. i believe that this must be controlled with `version` or cli

Re: Coding for solid state drives

2015-04-24 Thread tcak via Digitalmars-d
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

Re: Coding for solid state drives

2015-04-24 Thread Kagamin via Digitalmars-d
Shouldn't system cache apply appropriate sync policy?

Re: Coding for solid state drives

2015-04-24 Thread weaselcat via Digitalmars-d
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

Re: Coding for solid state drives

2015-04-24 Thread Vladimir Panteleev via Digitalmars-d
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

Re: Coding for solid state drives

2015-04-24 Thread Vladimir Panteleev via Digitalmars-d
On Friday, 24 April 2015 at 19:35:08 UTC, Walter Bright wrote: 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. That would be unwise - as HDDs are much slower (and still much more

Re: Coding for solid state drives

2015-04-24 Thread 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