On Dec 18, 2006, at 12:52 AM, Agent Zhang wrote:
On 12/18/06, Jesse Vincent <[EMAIL PROTECTED]> wrote:Is it that available_values isn't being cached? If so, would precachingit help?Okay, now I'd request caching the available_values sub (via an option?) since Benchmark::Timer has produced the following report:
So, I think the trick is that we may want something deeper: caching of Jifty::DBI::Collections. This would get us the performance boost here and elsewhere.
1 trial of total (20.610s total) 75 trials of available_values (13.864s total), 184.856ms/trial 75 trials of loop (2.126ms total), 28us/trial Calls of avalable_values are very expensive operations which take 67.3% of the total time. So it has nothing to do with the loop itself. I think caching is a very promising way to speed up things dramatically in this situation. Cheers, Agent _______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
