[pve-devel] stress testing pve api / pveproxy

[Stefan Priebe - Profihost AG]

Am 27.04.2017 um 19:12 schrieb Dietmar Maurer:
> Hi Stefan,
> 
> is this already solved? Or do you still observe that problem?

Thanks for asking. It seems to be a client related timeout. Not on PVE
side. But what i did not understand is that i don't see it if i raise

    $ua->timeout( $secs );

from 10 to 30 but the whole script only runs 1-3s on each run at all.
But it seems to work now.

Greets,
Stefan

> 
>> while stress testing the pve api i'm seeing pretty often a "500 read
>> timeout" response to my simple GET requests against the API.
>>
>> Around 1 out of 50 requests firing one request every 200ms wait for
>> answer fire next one.
>>
>> That one is coming from $response->status_line of a HTTP::Request->new()
>> object against the API.
>>
>> /usr/bin/pveproxy start -debug 1
>>
>> is printing many information especially not what is happening to my request.
>>
>> Any ideas? Well known bug? It's PVE 4.4.
>