Slawek provided a method to test it. Actually we tested it, checking the Neutron server memory consumption increased linearly every time we made a HTTP request.
Deploy OpenStack Neutron (without the fix, now present in all versions) and execute this (changing your server IP address):
$ i=1; while [ $i -lt 2000 ]; do echo "Request $i"; curl -g -i -X GET http://10.120.0.30:9696/v2.0/blabla -H "Accept: application/json" -H "User-Agent: openstacksdk/0.59.0 keystoneauth1/4.3.1 python-requests/2.26.0 CPython/3.6.8" -H "X-Auth-Token: $token" 2>1 >/dev/null; i=$(( i+1 )); sleep 0.01; done
You'll see how the Neutron server memory grows continuously.
Hello:
Slawek provided a method to test it. Actually we tested it, checking the Neutron server memory consumption increased linearly every time we made a HTTP request.
Deploy OpenStack Neutron (without the fix, now present in all versions) and execute this (changing your server IP address): 10.120. 0.30:9696/ v2.0/blabla -H "Accept: application/json" -H "User-Agent: openstacksdk/0.59.0 keystoneauth1/4.3.1 python- requests/ 2.26.0 CPython/3.6.8" -H "X-Auth-Token: $token" 2>1 >/dev/null; i=$(( i+1 )); sleep 0.01; done
$ i=1; while [ $i -lt 2000 ]; do echo "Request $i"; curl -g -i -X GET http://
You'll see how the Neutron server memory grows continuously.
Regards