Am 16.02.2015 um 16:50 schrieb Andreas Färber:
Am 16.02.2015 um 16:41 schrieb Stefan Priebe - Profihost AG:
Am 16.02.2015 um 15:49 schrieb Paolo Bonzini :
On 16/02/2015 15:47, Stefan Priebe - Profihost AG wrote:
Could it be that this is a results of compiling qemu with --enable-debug
to ge
Am 16.02.2015 um 16:49 schrieb Paolo Bonzini:
On 16/02/2015 16:41, Stefan Priebe - Profihost AG wrote:
Yes, just do nothing ("--enable-debug-info" is the default;
"--enable-debug" enables debug info _and_ turns off optimization).
If I do not enable-debug dh_strip does not extract any debuggi
On 16/02/2015 16:41, Stefan Priebe - Profihost AG wrote:
>> > Yes, just do nothing ("--enable-debug-info" is the default;
>> > "--enable-debug" enables debug info _and_ turns off optimization).
> If I do not enable-debug dh_strip does not extract any debugging symbols.
Then you need --disable-st
Am 16.02.2015 um 16:41 schrieb Stefan Priebe - Profihost AG:
>> Am 16.02.2015 um 15:49 schrieb Paolo Bonzini :
>>
>>
>>
>> On 16/02/2015 15:47, Stefan Priebe - Profihost AG wrote:
>>>
>>> Could it be that this is a results of compiling qemu with --enable-debug
>>> to get debugging symbo
> Am 16.02.2015 um 15:49 schrieb Paolo Bonzini :
>
>
>
> On 16/02/2015 15:47, Stefan Priebe - Profihost AG wrote:
>>
>> Could it be that this is a results of compiling qemu with --enable-debug
>> to get debugging symbols?
Yes.
>> *urg* my fault - sorry. Is there a way to
Hi,
> Am 16.02.2015 um 15:58 schrieb Andrey Korolyov :
>
> On Mon, Feb 16, 2015 at 5:47 PM, Stefan Priebe - Profihost AG
> wrote:
>> Hi,
>>> Am 16.02.2015 um 15:44 schrieb Paolo Bonzini:
>>>
>>>
On 16/02/2015 15:43, Stefan Priebe - Profihost AG wrote:
Hi,
> Am 16.02.2015 um
On 16/02/2015 15:47, Stefan Priebe - Profihost AG wrote:
>>> >>
>>> >> Could it be that this is a results of compiling qemu with --enable-debug
>>> >> to get debugging symbols?
>> >
>> > Yes.
> *urg* my fault - sorry. Is there a way to get debugging symbols without
> using enable-debug / getting
On Mon, Feb 16, 2015 at 5:47 PM, Stefan Priebe - Profihost AG
wrote:
> Hi,
> Am 16.02.2015 um 15:44 schrieb Paolo Bonzini:
>>
>>
>> On 16/02/2015 15:43, Stefan Priebe - Profihost AG wrote:
>>> Hi,
>>>
>>> Am 16.02.2015 um 13:24 schrieb Paolo Bonzini:
On 15/02/2015 19:46, Stefan Prie
Hi,
Am 16.02.2015 um 15:44 schrieb Paolo Bonzini:
>
>
> On 16/02/2015 15:43, Stefan Priebe - Profihost AG wrote:
>> Hi,
>>
>> Am 16.02.2015 um 13:24 schrieb Paolo Bonzini:
>>>
>>>
>>> On 15/02/2015 19:46, Stefan Priebe wrote:
while i get a constant random 4k i/o write speed of 20.000 io
On 16/02/2015 15:43, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> Am 16.02.2015 um 13:24 schrieb Paolo Bonzini:
>>
>>
>> On 15/02/2015 19:46, Stefan Priebe wrote:
>>>
>>> while i get a constant random 4k i/o write speed of 20.000 iops with
>>> qemu 2.1.0 or 2.1.3. I get jumping speeds with qemu
Hi,
Am 16.02.2015 um 13:24 schrieb Paolo Bonzini:
>
>
> On 15/02/2015 19:46, Stefan Priebe wrote:
>>
>> while i get a constant random 4k i/o write speed of 20.000 iops with
>> qemu 2.1.0 or 2.1.3. I get jumping speeds with qemu 2.2 (jumping between
>> 500 iops and 15.000 iop/s).
>>
>> If i use v
On 15/02/2015 19:46, Stefan Priebe wrote:
>
> while i get a constant random 4k i/o write speed of 20.000 iops with
> qemu 2.1.0 or 2.1.3. I get jumping speeds with qemu 2.2 (jumping between
> 500 iops and 15.000 iop/s).
>
> If i use virtio instead of virtio-scsi speed is the same between 2.2 an
H Stefan,
only for write ? or also read ?
I'll try to reproduce on my test cluster.
- Mail original -
De: "Stefan Priebe"
À: "qemu-devel"
Envoyé: Dimanche 15 Février 2015 19:46:12
Objet: [Qemu-devel] slow speed for virtio-scsi since qemu 2.2
Hi,
while i g
Hi,
while i get a constant random 4k i/o write speed of 20.000 iops with
qemu 2.1.0 or 2.1.3. I get jumping speeds with qemu 2.2 (jumping between
500 iops and 15.000 iop/s).
If i use virtio instead of virtio-scsi speed is the same between 2.2 and
2.1.
Is there a known regression?
Greets,
14 matches
Mail list logo
