Reviewed: https://review.opendev.org/746714 Committed: https://git.openstack.org/cgit/openstack/neutron-lib/commit/?id=024b5af64b69a6fb9eab7c5764d8f2b91f17ec2f Submitter: Zuul Branch: master
commit 024b5af64b69a6fb9eab7c5764d8f2b91f17ec2f Author: Slawek Kaplonski <[email protected]> Date: Tue Aug 18 15:13:36 2020 +0200 Log time of the apply_func only if it took more than 0.1 second It seems that logging start and end time of the neutron_lib.db.resource_extend.apply_func function is little bit too much for e.g. our gate as neutron-server logs are huge in such case. So lets use directly oslo_utils.timeutils.time_it() function and log end of such calls only if it will take more than 0.1 seconds. If function was executed in shorter time, it isn't really necessary to have it logged. Change-Id: I3931c4f7cac4df72d71403ebcaa6ec0b83756640 Closes-Bug: #1892017 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1892017 Title: Neutron server logs are too big in the gate jobs Status in neutron: Fix Released Bug description: As per email http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016579.html we should not log all time-cost entries in the server logs for every job. Maybe we can do it only in the rally based jobs and disable it everywhere else? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1892017/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
