[pve-devel] stress testing pve api / pveproxy

Stefan Priebe - Profihost AG s.priebe at profihost.ag
Tue Apr 25 19:54:36 CEST 2017


Hello,

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.

-- 
Thanks!
Stefan



More information about the pve-devel mailing list