> Since include directive is like C include. I originally though include > directive would always perform better than action include. For one > thread, include directive does perform better, but 2 threads action > include is twice as fast. One interesting observation with coyote > include directive for 1 thread is 95% of the responses were 30ms, but > the standard deviation or variance is almost 3x the mean. Other noteable > observations for 1 thread is include directive see dramatic fluctuations > in cpu and memory usage. This suggests JSP tags create and destroy lots > of objects associated with parsing and processing.
The 1 thread test could be really unpredictable (if GC happens, it will just stop all requests during that time, which will greatly increase the average). That's the only explnation I can think of. > include directive - 1 thread 1000 > ----------------- > httpconnector ave - 33 > cpu usage - 40-70 > coyote ave - 179 > cpu usage - 50-90% > > action include - 1 thread 1000 > ----------------- > httpconnector ave - 81 > cpu usage - 60-85% > coyote ave - 48 > cpu usage - 40-50% > > include directive - 2 threads 500 > ----------------- > httpconnector ave - 453 > cpu usage - 85-100% > coyote ave - 212 > cpu usage - 80-90% > > action include - 2 threads 500 > ----------------- > httpconnector ave - 299 > cpu usage - 80-100% > coyote ave - 89 > cpu usage - 50-80% Remy -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
