Hi Laszlo I 100% agree with both of your remarks. Caching is caching the entities, but also attempting to cache the list of entities. Batch updates is done as an infrastructure (change was reviewed and now in fixes) and after that - we can start using it everywhere.
----- Original Message ----- From: "Laszlo Hornyak" <lhorn...@redhat.com> To: "Liran Zelkha" <lzel...@redhat.com> Cc: "engine-devel" <engine-devel@ovirt.org> Sent: Tuesday, June 4, 2013 5:01:37 PM Subject: Re: [Engine-devel] Performance and scalability Hi Liran, Some comments to start the discussion: - Caching: exactly how is this resultset caching going to work? Wouldnt it be more simple to just cache the mapped entities? The mapping is not a big overhead, but caching the resultset seems to be difficult. - Batch updates: sounds cool, transactions are a major overhead on performance, so if you can make the update in a single tx and few interactions that will rock, but what if we keep the dynamic and statistic data in the memory at the first place and synchronize to DB on a background process. So that when you look for dynamic/statistics data, you do not have to hit the DB. Thx, Laszlo ----- Original Message ----- > From: "Liran Zelkha" <lzel...@redhat.com> > To: "engine-devel" <engine-devel@ovirt.org> > Sent: Tuesday, June 4, 2013 1:43:55 PM > Subject: [Engine-devel] Performance and scalability > > Hi all, > > I've added a new feature page for Performance and Scalability. Please review > and add your ideas... > http://www.ovirt.org/Features/Performance_And_Scalability > _______________________________________________ > Engine-devel mailing list > Engine-devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel > _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
