On 14 sep, 15:29, Ar Chron <[email protected]> wrote: > Is the app "overly-eager"? > > I ask because I have a compatriot who learned about eager loading, and > shazam! EVERYTHING was eager loaded... even stuff that wasn't needed at > the time.
Lol, I'll look into that, but I don't think this is the problem. And isn't eager loading data also only loaded when used? Again, I didn't develop this app, so it might take some time to look at all this (and it's probably coming out of my own time), so I'm just trying to gather some general info, also for future applications. > > As mentioned before, data is king, so profile to see what the real > hold-up is. > > And a +1 for discriminating caching... we knew our sidebar was > computationally busy (displays items related to the primary entity being > shown). That sidebar as a whole is cached, and the individual groups of > related types of items within the sidebar are cached as well. Depending > on the data content, views rendering cached fragments complete in 3% to > 10% of the time versus no cached data. I'll look into caching. I think things like stylesheets and javascripts are cached, but that doesn't really do anything for the application, I guess. The navigation can be cached, as it's pretty static. And the frontpage elements can also be cached, as it's not personalized and only updates when something new is added (which happens only once per 40 - 50 requests, I guess). That could help alot! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
