python-gnocchiclient

push runtime in benchmark seems off

Bug #1627825 reported by gordon chung
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-gnocchiclient
Triaged
Low
Unassigned

Bug Description

not sure reasoning but there are a few times when push runtime is the same or higher than another benchmark even though the push latency mean/median/95%/etc... are all significantly lower than other benchmark mark run.

i am running 32 workers client against 32 workers server api on separate 48CPU machines

Revision history for this message
gordon chung (chungg) wrote :

it also doesn't change in performance if i change client workers from 32 -> 24 -> 12 -> 8. it will push the same rate for all the workers. it does push slower when i drop workers to 2 though.

Revision history for this message
gordon chung (chungg) wrote :

just some more info. i tried switching it to ProcessPoolExecutor -> ThreadPoolExecutor and it performed better but still had same performance between 12->48 threads.

i then used 12 threads and ran 3 separate gnocchiclient processes using bash (aka 36 threads) and got consistent performance as running 12 threads with single process. so it seems like either max_workers isn't being honoured, or we process things too quickly that it never needs more than a 6-12 processes to get through 5K batch POST

Revision history for this message
Julien Danjou (jdanjou) wrote :

I had trouble to scaling the benchmark client. I tend to blame Python, but doing some profiling might help.

Changed in python-gnocchiclient:
status: New → Triaged
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.