I love this idea! Running benchmarks as we go will allow us to react quickly if there are unforeseen performance pain points.
Have you run anything similar to this proposal back in Pulp2 or elsewhere? I'm a little concerned about the storage capacity needed for the sheer number of sqlite3 databases generated. Maybe a script could periodically empty /var/lib/pulp/debug/ as it reaches certain configured size/age limits? --Dana Dana Walker Associate Software Engineer Red Hat <https://www.redhat.com> <https://red.ht/sig> On Mon, Sep 17, 2018 at 2:36 PM, Brian Bouterse <bbout...@redhat.com> wrote: > I'm interested in implementing a data collection feature for Pulp3. This > will allow us to easily and accurately benchmark pipeline performance to > clearly show improvement as we make changes. Borrowing from my old queueing > theory days... here is a data collection feature proposal: > > https://pulp.plan.io/issues/4021 > > Any comment/ideas are welcome. Thank you! > > -Brian > > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
