[Rt-devel] SQL/DBI caching
ruslan.zakirov at gmail.com
Mon Jul 6 17:36:22 EDT 2009
On Mon, Jul 6, 2009 at 6:11 PM, Alex Pilosov<alex at pilosoft.com> wrote:
> On Mon, 6 Jul 2009, Jesse Vincent wrote:
>> It's an area that can always see improvement.
> Well, so far, I've found that SearchBuilder will not do negative result
> caching (as in, if there's no entry for a certain query, it will keep
> re-querying repeatedly). Fixing that went from 120 queries to 80.
this is interesting patch to look at.
>> > I've hacked up enough things for DBD::Gofer caching support - and my
>> > display times went from 1s to .3s. Of course, this is not the right
>> > solution - DBIx::SearchBuilder should be more efficient in caching.
>> I'm not sure I agree with you, but I haven't seen the logs you're
>> working with. The danger of caching too agressively at the
>> SearchBuilder layer is that your cache isn't shared between multiple
>> processes and can quickly become stale/inaccurate.
>> I look forward to more details of your analysis. I'd be thrilled to see
>> improvements in this area.
> I was kind of hoping someone would have done this already. :)
We did a lot of in that area and keep doing. It's often better to fire
several fast queries instead of one big in some cases, but anyway
better caching is welcome.
> List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
Best regards, Ruslan.
More information about the Rt-devel