<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 6, 2014 at 11:22 AM, Itamar Heim <span dir="ltr"><<a href="mailto:iheim@redhat.com" target="_blank">iheim@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 class="">On 04/03/2014 07:51 PM, Liran Zelkha wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The problem is with both updates and selects.<br>
For selects - to get all the information for the VDS we have multiple<br>
joins. Adding another one will hurt performance even more.<br>
For updates - we have vds_static thats hardly changed. vds_statistics<br>
that changes all the time. vds_dynamic is not changed allot - but is<br>
updated all the time because of the status. I think it's best to split<br>
it to the two existing tables (BTW - relevant for VM as well)<br>
</blockquote>
<br></div>
but we don't update it unless the status has changed, which is a rare occurance?<br>
</blockquote></div>Actually - no. We can definitely see times we are updating vds_dynamic with no reason at all. I tried to create patches for that - but it happens from many different places in the code.</div></div>