plugin code?
*From:* Deej Howard [mailto:deej.how...@neulion.com]
*Sent:* Tuesday, December 19, 2017 9:17 AM
*To:* 'Brian Bouterse' <bbout...@redhat.com>
*Cc:* 'pulp-list' <pulp-list@redhat.com>
*Subject:* RE: [Pulp-list] REST API performance-related question(s)
I’m no Python guru, so that’s entirely possible)?
*From:* Brian Bouterse [mailto:bbout...@redhat.com]
*Sent:* Monday, December 18, 2017 3:59 PM
*To:* Deej Howard <deej.how...@neulion.com>
*Cc:* pulp-list <pulp-list@redhat.com>
*Subject:* Re: [Pulp-list] REST API performance-relate
Is there some way you can post the cProfile data? If you don't have a place
to post, one option may be to file an issue at pulp.plan.io.
Consider using one of these tools [4] to look for the line of Pulp code
that has the longest cumulative time. The tools provide sorting so that
should be easy.
Hoping to follow up on my own questions, I attempted to
take advantage of the cProfile functionality[3] against a new run of my
cleanup script (profiling was enabled within the Apache/Pulp container to
get data on the server side). This run had an even more isolated run-time
data
Hi, I’m using the 2.14.3 release in a Docker-based
configuration (details below), and I’ve noticed some performance-related
issues in a script-based artifact cleanup job that is run on a daily
basis. The artifacts in question are of our own construction, incorporated
via the Pulp
