<div dir="ltr">Cool, thanks for the clarification. Sounds great.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0;padding:0;font-size:14px;text-transform:uppercase;margin-bottom:0"><span>Dana</span> <span>Walker</span></p>
<p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:#aaa;margin:0"></span></p>
<p style="font-weight:normal;margin:0;font-size:10px;color:#999"><a style="color:#0088ce;font-size:10px;margin:0;text-decoration:none;font-family:'overpass',sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p>
<table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td>
</tr></tbody></table>
</div></div></div></div>
<br><div class="gmail_quote">On Wed, Sep 19, 2018 at 1:04 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><br><br><div class="gmail_quote"><span class=""><div dir="ltr">On Mon, Sep 17, 2018 at 3:10 PM Dana Walker <<a href="mailto:dawalker@redhat.com" target="_blank">dawalker@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>I love this idea! Running benchmarks as we go will allow us to react quickly if there are unforeseen performance pain points.</div></div></blockquote></span><div>Sweet! <br></div><span class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>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 <code>/var/lib/pulp/debug/</code> as it reaches certain configured size/age limits?</div></div></blockquote></span><div>We did have a similar feature in Pulp2 that would output a cProfile with the filename being the task UUID. (docs link below). I don't think storage wasn't an issue there, but users would have to confirm for us. When users would use it, they would turn the feature on, run the troublesome workload, then turn it off again so it's usually a few tasks only. I think each db will be very small < 1MB probably.<br></div><div><br></div><div><a href="https://docs.pulpproject.org/dev-guide/debugging.html#task-performance-analysis" target="_blank">https://docs.pulpproject.org/<wbr>dev-guide/debugging.html#task-<wbr>performance-analysis</a><br></div><span class=""><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>--Dana<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-6796703501643793221gmail-m_4497099943094623026m_-5981500015829887393gmail_signature"><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-size:14px;text-transform:uppercase"><span>Dana</span> <span>Walker</span></p>
<p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:rgb(170,170,170);margin:0px"></span></p>
<p style="font-weight:normal;margin:0px;font-size:10px;color:rgb(153,153,153)"><a style="color:rgb(0,136,206);font-size:10px;margin:0px;text-decoration:none;font-family:"overpass",sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p>
<table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td>
</tr></tbody></table>
</div></div></div></div>
<br><div class="gmail_quote">On Mon, Sep 17, 2018 at 2:36 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">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:</div><div dir="ltr"><br></div><div dir="ltr"><a href="https://pulp.plan.io/issues/4021" target="_blank">https://pulp.plan.io/issues/<wbr>4021</a></div><div dir="ltr"><br></div><div>Any comment/ideas are welcome. Thank you!<span class="m_-6796703501643793221gmail-m_4497099943094623026m_-5981500015829887393HOEnZb"><font color="#888888"><br></font></span></div><span class="m_-6796703501643793221gmail-m_4497099943094623026m_-5981500015829887393HOEnZb"><font color="#888888"><div><br></div><div>-Brian<br></div></font></span></div>
<br>______________________________<wbr>_________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></span></div></div></div>
</blockquote></div><br></div>