At Sat, 29 May 2010 09:43:35 +0100,
Gordan Bobic wrote:
Jiro SEKIBA wrote:
2) Mechanical disks suffer from slow random writes (or any random
operation for that matter), too. Do the benefits of nilfs show in random
write performance on mechanical disks?
I think it may have benefits,
Hi,
At Fri, 28 May 2010 10:50:31 +0100,
Gordan Bobic wrote:
Jiro SEKIBA wrote:
I haven't got any particular quantitative data by my own,
so I'll write somewhat subjective opinion.
Thanks, I appreciate it. :)
I've got a somewhat broad question on the suitability of nilfs for
Hi,
On 05/29/10 09:31, Jiro SEKIBA wrote:
Hi,
At Fri, 28 May 2010 10:50:31 +0100,
Gordan Bobic wrote:
Jiro SEKIBA wrote:
I haven't got any particular quantitative data by my own,
so I'll write somewhat subjective opinion.
Thanks, I appreciate it. :)
I've got a
Vincent Diepeveen wrote:
1) Modern SSDs (e.g. Intel) do this logical/physical mapping
internally, so that the writes happen sequentially anyway.
Could you explain that, as far as i know modern SSD's have 8 independant
channels to do read and writes, which is why they are having that big
On May 28, 2010, at 11:24 AM, Gordan Bobic wrote:
Vincent Diepeveen wrote:
1) Modern SSDs (e.g. Intel) do this logical/physical mapping
internally, so that the writes happen sequentially anyway.
Could you explain that, as far as i know modern SSD's have 8
independant channels to do read
Vincent Diepeveen wrote:
1) Modern SSDs (e.g. Intel) do this logical/physical mapping
internally, so that the writes happen sequentially anyway.
Could you explain that, as far as i know modern SSD's have 8
independant channels to do read and writes, which is why they are
having that big read
Vincent Diepeveen wrote:
1) Modern SSDs (e.g. Intel) do this logical/physical mapping
internally, so that the writes happen sequentially anyway.
Could you explain that, as far as i know modern SSD's have 8
independant channels to do read and writes, which is why they are
having that big read
I've got a somewhat broad question on the suitability of nilfs for
various workloads and different backing storage devices. From what I
understand from the documentation available, the idea is to always write
sequentially, and thus avoid slow random writes on old/naive SSDs. Hence
I have a few
