> OK. I finally got the spreadsheet working and have results. Below is > the data based on a run from the build before the most recent. Ill > have to go get the latest build this week and rerun overnight to > generate data but the analysis will be very very fast since I can now > just dump log file records into the spreadsheet and get the data below.
Very cool! I really like the analysis - I think you just set the gold standard for comparison tests. > I am still chewing on what the information below means ;-) Have you had a chance to look at the contents of any of the really slow pages? Bad Case 2 (was slow but it was acceptable, now it's not) is particularly interesting because of the small number of pages in this category. Here's my profiling technique [1] if you want to get out the microscope. If you can provide the data, I can do the analysis, too. I'm interested to hear what you have to say. I have been thinking very hard about how to add output caching to FlexWiki in the new design. It's decidedly nontrivial, but I'm increasingly convinced that there's a reasonable way to do it, where "reasonable" is defined as "does not produce spaghetti code". However, if we can ship 2.0 without it, that would be good - output caching could be a 2.2 feature. *If* I can pull it off, I think we'll find that it makes an *enormous* difference in performance in cases where WikiTalk can be cached (e.g. doesnt call DateTime.Now). If we don't think we can ship 2.0 without output caching, then I think maybe we should ship the current bits as Beta 3, and that www.flexwiki.com should be upgraded as well. I just really think we need to keep putting out "official" releases every three months or less - it's apparent from the questions that we get here that many people never visit http://builds.flexwiki.com, and a SourceForge "last updated" date way in the past is the kiss of death. [1] - Download NProf - Build RenderDriver from the FlexWiki tools directory - In NProf, set RenderDriver.exe to be the executable - In NProf set the arguments to be "\path\to\flexwiki.config Namespace.TopicName n" where n is a number. I suggest 2 as a good start. - Run by pressing F5 - After run completes, drill down into Main->Run to see where the time went. Or Main->Warmup if you want to see what happened before the cache was populated. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Flexwiki-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flexwiki-users
