commit 1c39f8fabf8ed44e0de563893d5813be1bf7b5e3
Author: ZhiQiang Fan <email address hidden>
Date: Wed Mar 18 17:37:54 2015 +0800
Don't record time when self.timing is False
The expected behavior is when timing is True, then we record each
request's time, then we should call reset_timings() to release memory.
However, the shell, client.{HTTPClient,SessionClient} will record each
request's time no matter what timing is set, then after long running
time in service like ceilometer-agent-compute, the memory keeps increasing.
We'd better not record request's time when timing is set to False.
Users are not responiable to call reset_timings() when they don't want
timing functionality.
Reviewed: https:/ /review. openstack. org/165343 /git.openstack. org/cgit/ openstack/ python- novaclient/ commit/ ?id=1c39f8fabf8 ed44e0de563893d 5813be1bf7b5e3
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1c39f8fabf8ed44 e0de563893d5813 be1bf7b5e3
Author: ZhiQiang Fan <email address hidden>
Date: Wed Mar 18 17:37:54 2015 +0800
Don't record time when self.timing is False
The expected behavior is when timing is True, then we record each
request's time, then we should call reset_timings() to release memory.
However, the shell, client. {HTTPClient, SessionClient} will record each agent-compute, the memory keeps increasing.
request's time no matter what timing is set, then after long running
time in service like ceilometer-
We'd better not record request's time when timing is set to False.
Users are not responiable to call reset_timings() when they don't want
timing functionality.
Change-Id: I3e7d2fadf9a21b e018781d528a1b6 562228da6dd
Closes-Bug: #1433491