Hi, We're working on a struts application running on Websphere 3.5.4. I was doing some performance testing when I noticed that it consumed a whole lot of memory which I couldn't really explain. So I ran the application supervised by JProbe and discovered some interesting things.
On one of the JSP's there were nearly 50 000 object created of the class java.beans.MethodDescriptor and half as many of java.beans.PropertyDescriptor. This made my investigate things further, and I bottled down a JSP with only a simple <bean:write name="testBean" property="value"/> - tag in it. On a request to this JSP I got these results: java.beans.MethodDescriptor: 106 objects á 36 bytes (3816bytes) java.beans.PropertyDescriptor: 35 objects á 52 bytes (1820bytes) The upmost rows of the trace looked like this: GenericBeanInfo.<init>(GenericBeanInfo) Introspector.getBeanInfo(Class); JspRuntimeLibrary.introspecthelper(Object, String, String, ServletRequest, String, boolean) _test_jsp_0_jspService(HttpServletRequest, HttpServletResponse) And this is just for the simple "write" tag. The iterate tag generated over 700 objects of the MethodDescriptor class. What I did then, was to run the same investigation using the Tomcat4 (latest binary production release) and what I found was... no objects at all of these classes was created!! The conclusion here must be that the Websphere servlet engine must produce a lot of overhead using the tags. This is of real concern on a site with some real load to it. Has anyone running Struts on Websphere noticed these oddities as well or maybe explain the reason for this? /Johannes _____________________________________________________ Hitta snörapporter... frĺn 500 olika skidorter i Europa pĺ http://se.snow.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
