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" <lzelkha(a)redhat.com>
To: "engine-devel" <engine-devel(a)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(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel