<div dir="ltr">I would be happy if we can lose vds_dynamic all together, and just keep vds_static and vds_statistics. Our performance will be happy too ;-)<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Apr 3, 2014 at 4:33 PM, Eli Mesika <span dir="ltr"><<a href="mailto:emesika@redhat.com" target="_blank">emesika@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
----- Original Message -----<br>
> From: "Gilad Chaplik" <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>><br>
> To: "Yair Zaslavsky" <<a href="mailto:yzaslavs@redhat.com">yzaslavs@redhat.com</a>><br>
> Cc: "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> Sent: Thursday, April 3, 2014 4:00:25 PM<br>
> Subject: Re: [Engine-devel] vds_dynamic refactor<br>
><br>
> ----- Original Message -----<br>
> > From: "Yair Zaslavsky" <<a href="mailto:yzaslavs@redhat.com">yzaslavs@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>>, "engine-devel"<br>
> > <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> > Sent: Thursday, April 3, 2014 2:12:59 PM<br>
> > Subject: Re: [Engine-devel] vds_dynamic refactor<br>
> ><br>
> ><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: "engine-devel" <<a href="mailto:engine-devel@ovirt.org">engine-devel@ovirt.org</a>><br>
> > > Sent: Thursday, April 3, 2014 2:04:29 PM<br>
> > > Subject: Re: [Engine-devel] vds_dynamic refactor<br>
> > ><br>
> > > Why not move it to vds_static?<br>
> ><br>
> > +1 on Liran's comment.<br>
<br>
+1 as well , vds_static is the place for that<br>
<br>
> > I would prefer not to add more complexity to the vds tables family.<br>
> > Such complexity may effect performs of queries/views.<br>
> > If you wish, you can create a view on top of vds_static named vds_on_boot<br>
> > for<br>
> > querying of vds on boot info.<br>
> ><br>
> > Yair<br>
><br>
> That means moving almost all of vds_dynamic into vds_static except of memory,<br>
> pending resources and status (maybe more but not much);<br>
> and there will not be any db separation between user input and on_boot data.<br>
<br>
Why we should have such separation ?<br>
<br>
><br>
> Thanks,<br>
> Gilad.<br>
><br>
> ><br>
> > ><br>
> > ><br>
> > > On Thu, Apr 3, 2014 at 2:00 PM, Gilad Chaplik <<a href="mailto:gchaplik@redhat.com">gchaplik@redhat.com</a>><br>
> > > wrote:<br>
> > ><br>
> > > > Hi list,<br>
> > > ><br>
> > > > I propose to split vds_dynamic table into 2 tables:<br>
> > > > - vds_dynamic<br>
> > > > - vds_on_boot<br>
> > > > We need a place to put all non-dynamic data that gets updated once the<br>
> > > > host is booted, and I think dynamic isn't the place for it.<br>
> > > > In first phase we will put there NUMA host topoplogy, but later on<br>
> > > > migrate<br>
> > > > all non-dynamic host data (cpu, os, etc.).<br>
> > > ><br>
> > > > thoughts?<br>
> > > ><br>
> > > > Thanks,<br>
> > > > Gilad.<br>
> > > > _______________________________________________<br>
> > > > Engine-devel mailing list<br>
> > > > <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> > > > <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
> > > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Engine-devel mailing list<br>
> > > <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> > > <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
> > ><br>
> ><br>
> _______________________________________________<br>
> Engine-devel mailing list<br>
> <a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
><br>
_______________________________________________<br>
Engine-devel mailing list<br>
<a href="mailto:Engine-devel@ovirt.org">Engine-devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/engine-devel" target="_blank">http://lists.ovirt.org/mailman/listinfo/engine-devel</a><br>
</blockquote></div><br></div></div>