technology | writing | life
technology | writing | life |
|
|
Wednesday, April 21, 2004
"I'm trying to optimize a web application which is build totally around XSLT, something like a homegrown Cocoon. Every page basically is a set of one or more transformations and application is spending 80+% of the time running XSLTs. Java profiler is not much help because system is
basically interpreting an execution defined in terms of XSLT. I would like to have something like a XSLT profiler that will give me a "hot spots" statistics. Can anybody share their experience on dealing with something like it. Any ideas, insights or pointers are greatly appreciated. I'm also looking for any good resources on speeding up XSLT based applications and real life experience with XSLTC." - as seen on a user group mailing list I'm subscribed to. XML is great for data interchange, but not so great for execution. It's the old trap, seen over and over - it's easy to build a platform for editing, XML makes it easy for parsing, but you can't forget about those old saws, debugging and profiling. |
03/30/2003 - 04/06/2003 05/04/2003 - 05/11/2003 01/11/2004 - 01/18/2004 01/18/2004 - 01/25/2004 01/25/2004 - 02/01/2004 02/01/2004 - 02/08/2004 02/15/2004 - 02/22/2004 02/29/2004 - 03/07/2004 03/07/2004 - 03/14/2004 03/14/2004 - 03/21/2004 03/28/2004 - 04/04/2004 04/18/2004 - 04/25/2004 05/23/2004 - 05/30/2004 05/30/2004 - 06/06/2004 06/13/2004 - 06/20/2004 06/27/2004 - 07/04/2004 03/27/2005 - 04/03/2005 06/05/2005 - 06/12/2005 07/31/2005 - 08/07/2005 10/09/2005 - 10/16/2005 01/29/2006 - 02/05/2006 04/02/2006 - 04/09/2006 06/04/2006 - 06/11/2006 06/25/2006 - 07/02/2006 08/27/2006 - 09/03/2006 12/17/2006 - 12/24/2006 01/21/2007 - 01/28/2007 07/19/2009 - 07/26/2009
No need to by shy - make contact!
Copyright © 2003-2004 Will Iverson. All rights reserved.
