Hi, after profiling my lift application (which uses the mapper classes) I found out that most of the time is spend doing SQL queries. Displaying medium-sized tabular data executes hundreds of (mostly small) queries. This takes a lot of time.
I understand that the mapper implementation is not optimized. - Is there any way for me to optimize this? E.g. enabling caching, enabling something like prefetching, ... ? - Did anyone do db query profiling / optimization with lift before? What have the results been? - What is a good way to cache queries generated by MetaMapper.find() and findAll() ? Thank you for your patience - I'm still a lift learner :) Joachim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
