On 02/26/2013 10:30 AM, Yair Zaslavsky wrote:
> The next step is, by my opinion, is start to use cache for not
often
> >changed object, VdsGroup is classical example of
> >such object.
+1 - and another issue I wanted to take a look into - Please notice we have entities
representing views.
I have a feeling we abuse VM (for example) too much - we use AuditLoggableBase to
"cache" vm - but still - I bet that in some flows
we don't need the entire VM -> we might need only static (or dynamic part) of it.
We should take a look into this as well . Getting vm dynamic from db instead of vm means
less joins.
Same applies for vds and storage_domains
lets be careful with adding caches - I'm not sure lightweight queries to
the db, which probably has this in its cache are a critical bottleneck,
while adding caches adds potential for bugs, and will make it harder to
scale out.