Am 13.04.2015 um 14:28 hat ein geschrieben:
> Dear Fam,
>
> Check out my update please:
> http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg01318.html
>
> Using aio=native,cache=none results in 500%-2000% performance drop comparing
> to
> bare metal and 300%-1000% comparing to aio=threa
On 13/04/2015 14:28, ein wrote:
>
>
> Check out my update please:
> http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg01318.html
>
> Using aio=native,cache=none results in 500%-2000% performance drop
> comparing to bare metal and 300%-1000% comparing to
> aio=threads,cache=unsafe.
No
Dear Fam,
Check out my update please:
http://lists.nongnu.org/archive/html/qemu-devel/2015-04/msg01318.html
Using aio=native,cache=none results in 500%-2000% performance drop
comparing to bare metal and 300%-1000% comparing to
aio=threads,cache=unsafe.
I'd like to know what numbers should I expe
On Fri, 04/10 22:38, ein wrote:
> Qemu creates more than 70 threads and everyone of them tries to write to
> disk, which results in:
> 1. High I/O time.
> 2. Large latency.
> 2. Poor sequential read/write speeds.
>
> When I limited number of cores, I guess I limited number of threads as
> well. Th
On 04/11/2015 03:09 PM, Paolo Bonzini wrote:
> On 10/04/2015 22:38, ein wrote:
>> Qemu creates more than 70 threads and everyone of them tries to write to
>> disk, which results in:
>> 1. High I/O time.
>> 2. Large latency.
>> 2. Poor sequential read/write speeds.
>>
>> When I limited number of cor
On 10/04/2015 22:38, ein wrote:
>
> Qemu creates more than 70 threads and everyone of them tries to write to
> disk, which results in:
> 1. High I/O time.
> 2. Large latency.
> 2. Poor sequential read/write speeds.
>
> When I limited number of cores, I guess I limited number of threads as
> wel
