[PATCH conductor 0/1] #794759 - Fix absurdly-inefficient pool family page

Justin Clift jclift at redhat.com
Fri Feb 17 17:14:48 UTC 2012


On 18/02/2012, at 3:47 AM, Matt Wagner wrote:
<snip>
> Because Rails caches SQL queries, this wasn't as disastrous as it could be, but it was still bad.
> 
> This patch greatly improves the situation, though it's not perfect. We do hit the query cache a few times in a few harder-to-avoid cases, but hitting the query cache "a few times" doesn't seem problematic. (That's what it's there for.) It also doesn't quite feel right to be calling this from a view at all, but it's not trivial to avoid with the way the code is written and I was reluctant to make major changes there.
> 
> A quick comparison with and without this change, in development mode (where nothing is fast) shows that the average page load time drops from around 1900ms to about 950ms. That's hardly a scientific benchmark, but I'll take a 100% speedup any day...

Would a materialised view make sense for this?  i.e. updated every XYZ amount of time (whatever is appropriate)

+ Justin

> -- Matt

--
Aeolus Community Manager
http://www.aeolusproject.org




More information about the aeolus-devel mailing list