You can use recent builds of DebugKit to check on the rendering time of all your elements. It tracks all the element rendering time separately. And Graham Weldon, even added a feature for little bar charts to be generated, giving you a more visual way to see the cost of your elements.
-Mark On Feb 8, 8:07 am, Abhimanyu Grover <[email protected]> wrote: > Yea, I've just implemented element level caching - however I'm still > keeping a close eye on rendering process. > > Thanks for reply. > > On Feb 8, 11:42 am, "[email protected]" <[email protected]> wrote: > > > Hi, > > > I haven't done any very heavy element rendering myself, but I know > > that element output can be cached if suitable for your application, > > which would help you out a lot. > > > Pete > > > On Feb 7, 9:36 pm, Abhimanyu Grover <[email protected]> wrote: > > > > Also, I would like to add, there is no requestAction() used in these > > > helpers. They just make use of Html and Form helper to output blocks > > > to the CMS. > > > > On Feb 8, 2:31 am, Abhimanyu Grover <[email protected]> wrote: > > > > > Hi there again, > > > > > As our application grows more and more, no. of elements used per page > > > > are increasing day by day. Right now we're at avg. 5 elements per > > > > page. What do you guys think of it? > > > > > Elements, for sure would slow down the app a bit, but what are your > > > > views on it? How many elements are too many? > > > > > Thanks for reading! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
