On Tue, Dec 07 2010, Lars Magne Ingebrigtsen wrote: >> Nothing has ever been slow in shr, to my eyes. > > In my work capacity, I get email from marketers (peeps wanna sell us > stuff! how rude!), and they have tools that generate these HTML table > monstrosities. One of them take like ten seconds to render. (Before I > put the table rendering cache thing in it took several minutes.) That just prove your cache implementation of the table rendering is a good choice. Without any profiling of the code, there is no way to know how to optimize the table rendering further then. And this does not back up your previous statement: > A 90% solution that's fast enough to actually use is infinitely more > useful than a 100% solution that's so slow that you can't use it. Table > rendering (if you have nested tables) is already so slow that it's > painful, and that has to be fixed. Doing