I did - i'm getting 5 minute load times almost exclusively as a result of Kid. The site is almost all widget based, so without refactoring to remove the widgets I can't really tell how much is just Kid being slow and how much is the widgets being slow.
GothCandy.com uses stupidly complex Kid templates with many, many match tags, few images, nothing but widgets for rendering of visual components, and every page is "poorly" database driven - caching is nearly non-existent.
Using the Firefox Firebug extension, I benchmarked various pages on the site. The first number is the amount of time it took for TurboGears / Kid to generate the base HTML. The second number is the total amount of time to load the page including downloading secondary elements (CSS, images, JS, etc.) and initialize JavaScript.
Front page: 4ms / 330ms Front page, no cache: 4ms / 1.64s Blog listing, newest five: 4ms / 337ms Blog listing, all 2007 entries: 4ms / 364ms Blog listing, all 2007 entries, no cache: 4ms / 1.05s Blog listing, all 2006 entries: 54ms / 351ms Blog listing, all 2006 entries, no cache: 66ms / 1.57sNew blog entry form: 4ms / 24.49s - multiple un-optimized JavaScript files
I need to rewrite some of that javascript... my customized widgEditor takes a -long- time to start up, as does the calendar pop-down widget's JS...
Matthew Bevan, Systems Administrator Top Floor Computer Systems Ltd.
smime.p7s
Description: S/MIME cryptographic signature
