bytehd wrote: > what maint tasks are killing ASSP? None. They are "blocking" it. Basically there are some tasks that, while they are being run, cause ASSP do to nothing else.
> can you provide a listing of functions and execution times for a given load? > sorted by time? > (not asking for much huh) > Guess im coming from the great app dev tools you get on the winblows side Go look at the processing order, for the most part it's in order of least to most in terms of CPU usage. > to MT, generally you are looking at encapsulating anything that can run with > local vars into its own object. > sharing anything means you need locking eventually, then you're back to > slowdowns. Most of the maintenance tasks are fairly self contained but the spam tests are pretty bad about global vars. :( > what is your version based on > 1.3.3.8 I hope 1.3.5 most likely. 1.3.3.8 is missing many new features and any code written for it would most likely NOT work in 1.3.5. Kevin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
