OK, I was able to identify the bug in the FlexWiki 2.0 code that was
destabilizing my performance tests. Apparently, throwing an uncaught
exception on the newsletter thread plays real havoc with ASP.NET under IIS6.
Fixed. As a result, I'm able to run a complete set of tests against both
FlexWiki 1.8 and 2.0. The comparison is still pretty stark: typical
execution (Time to First Byte - TTFB) times on 1.8 are 200-500 milliseconds,
with typical TTFB times on FW 2.0 more like 5000 ms. So I've got an order of
magnitude or so to fix. At least I was able to profile 2.0 to get some idea
where the bottleneck is, and it's exactly where I expected: parsing
properties out of a page body. I'll add caching there, see how much it
helps, and run the numbers again.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
