Bump
2017-02-10 22:11 GMT+08:00 Mikael :
> 2017-02-10 18:39 GMT+08:00 David Gwynne :
>
>> > 2017-02-09 16:41 GMT+08:00 David Gwynne :
>>
> ..
>
>> i can go into more detail if you want.
>>
>> cheers,
>> dlg
>>
>
> Hi David,
>
>
2017-02-10 18:39 GMT+08:00 David Gwynne :
> > 2017-02-09 16:41 GMT+08:00 David Gwynne :
>
..
> i can go into more detail if you want.
>
> cheers,
> dlg
>
Hi David,
Thank you - yes please go into more detail!
Also on a more concrete level I would be the
> On 9 Feb 2017, at 7:11 pm, Mikael wrote:
>
> 2017-02-09 16:41 GMT+08:00 David Gwynne :
> ..
> hey mikael,
>
> can you be more specific about what you mean by multiqueuing for disks? even
a
> reference to an implementation of what you’re asking about
2017-02-09 16:41 GMT+08:00 David Gwynne :
..
> hey mikael,
>
> can you be more specific about what you mean by multiqueuing for disks?
> even a
> reference to an implementation of what youâre asking about would help me
> answer this question.
>
> ill write up a bigger reply
> On 9 Feb 2017, at 12:42 pm, Mikael wrote:
>
> Hi misc@,
>
> The SSD reading benchmark in the previous email shows that per-device
> multiqueuing will boost multithreaded random read performance very much
> e.g. by ~7X+, e.g. the current 50MB/sec will increase to
Hi misc@,
The SSD reading benchmark in the previous email shows that per-device
multiqueuing will boost multithreaded random read performance very much
e.g. by ~7X+, e.g. the current 50MB/sec will increase to ~350MB/sec+.
(I didn't benchmark yet but I suspect the current 50MB/sec is system-wide,
6 matches
Mail list logo