<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 6, 2014 at 3:37 PM, Kobi Ianko <span dir="ltr"><<a href="mailto:kobi@redhat.com" target="_blank">kobi@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Joining in...<br>
>From my point of view, in real life a user should have that many VDSs on one Engine (from a DB point of view).<br>
Modern DB system handles tables with millions of records and many relations, Do we really have a performance issue here?<br>
We could prefer a more easy to maintain implantation in this case over DB performance<br>
<div class=""><br></div></blockquote><div>Yes we do. We make many queries on the VDS view, which is a VERY complex view. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
<br>
----- Original Message -----<br>
> From: "Gilad Chaplik" <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>><br>
> To: "Liran Zelkha" <<a href="mailto:liran.zelkha@gmail.com">liran.zelkha@gmail.com</a>><br>
</div><div><div class="h5">> Cc: <a href="mailto:devel@linode01.ovirt.org">devel@linode01.ovirt.org</a>, "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> Sent: Sunday, April 6, 2014 3:32:26 PM<br>
> Subject: Re: [Devel] [Engine-devel] vds_dynamic refactor<br>
><br>
> ----- Original Message -----<br>
> > From: "Liran Zelkha" <<a href="mailto:liran.zelkha@gmail.com">liran.zelkha@gmail.com</a>><br>
> > To: "Gilad Chaplik" <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>><br>
> > Cc: "Itamar Heim" <<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>>, <a href="mailto:devel@linode01.ovirt.org">devel@linode01.ovirt.org</a>,<br>
> > "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> > Sent: Sunday, April 6, 2014 3:26:24 PM<br>
> > Subject: Re: [Engine-devel] vds_dynamic refactor<br>
> ><br>
> > On Sun, Apr 6, 2014 at 3:18 PM, Gilad Chaplik <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>> wrote:<br>
> ><br>
> > > ----- Original Message -----<br>
> > > > From: "Itamar Heim" <<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>><br>
> > > > To: "Liran Zelkha" <<a href="mailto:liran.zelkha@gmail.com">liran.zelkha@gmail.com</a>><br>
> > > > Cc: "Gilad Chaplik" <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>>, <a href="mailto:devel@linode01.ovirt.org">devel@linode01.ovirt.org</a>,<br>
> > > "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> > > > Sent: Sunday, April 6, 2014 11:33:12 AM<br>
> > > > Subject: Re: [Engine-devel] vds_dynamic refactor<br>
> > > ><br>
> > > > On 04/06/2014 11:32 AM, Liran Zelkha wrote:<br>
> > > > ><br>
> > > > ><br>
> > > > ><br>
> > > > > On Sun, Apr 6, 2014 at 11:22 AM, Itamar Heim <<a href="mailto:iheim@redhat.com">iheim@redhat.com</a><br>
> > > > > <mailto:<a href="mailto:iheim@redhat.com">iheim@redhat.com</a>>> wrote:<br>
> > > > ><br>
> > > > > On 04/03/2014 07:51 PM, Liran Zelkha wrote:<br>
> > > > ><br>
> > > > > The problem is with both updates and selects.<br>
> > > > > For selects - to get all the information for the VDS we have<br>
> > > > > multiple<br>
> > > > > joins. Adding another one will hurt performance even more.<br>
> > > > > For updates - we have vds_static thats hardly changed.<br>
> > > > > vds_statistics<br>
> > > > > that changes all the time. vds_dynamic is not changed allot -<br>
> > > but<br>
> > > > > is<br>
> > > > > updated all the time because of the status. I think it's best<br>
> > > to<br>
> > > > > split<br>
> > > > > it to the two existing tables (BTW - relevant for VM as well)<br>
> > > > ><br>
> > > > ><br>
> > > > > but we don't update it unless the status has changed, which is a<br>
> > > > > rare occurance?<br>
> > > > ><br>
> > > > > Actually - no. We can definitely see times we are updating<br>
> > > > > vds_dynamic<br>
> > > > > with no reason at all. I tried to create patches for that - but it<br>
> > > > > happens from many different places in the code.<br>
> > > ><br>
> > > > what would be updated vds_dyanmic for status not originating in update<br>
> > > > run time info?<br>
> > ><br>
> > > We have separate DB flows for that (updateStatus and<br>
> > > updatePartialVdsDynamicCalc and more in VdsDynamicDAODbFacadeImpl).<br>
> > > A question: do you know if we update status in updateVdsDynamic? :-) not<br>
> > > sure but I found a possible race for pending resources (cpu, mem), LOL<br>
> > > :-)<br>
> > ><br>
> > > I think we do but not sure. Will check.<br>
><br>
> Of course it is, that was a rhetorical question :-) (a lot of emoticons and<br>
> LOLs ;-))<br>
><br>
> ><br>
> ><br>
> > > Still holds my original thought for having vds_on_boot.<br>
> > ><br>
> > ><br>
> > ><br>
> > Let's talk f2f on Tuesday?<br>
><br>
> I'd prefer to reach conclusions here, I'd like everyone to be involved in a<br>
> root issue like this one.<br></div></div></blockquote><div><br></div><div>What is the update frequency of this field? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div class="h5">
><br>
> ><br>
</div></div>> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/devel</a><br>
><br>
</blockquote></div><br></div></div>