Re: Profiling the memory usage
On 10/16/07, Nino Saturnino Martinez Vazquez Wael <[EMAIL PROTECTED]> wrote: > Well said:) Sometimes I just take a wrong turn while wanting to explain > something, and get stuck in that idea. > > About the wicket-objectsizeof-agent, could it be used to make a small > wicket diagnostics contribution..? I mean can it walk over live wicket > applications and tell how much individual part were using? Or are some > one already doing this? You could implement this through a custom session store. The wicket-objectsizeof-agent project only plugs in a 'IObjectsSizeOfStrategy' that is based on instrumentation rather then serialization. That strategy is used by org.apache.wicket.util.lang.Objects#sizeOf(Object). But again, using a profiler is probably much easier and gives better results. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Profiling the memory usage
Well said:) Sometimes I just take a wrong turn while wanting to explain something, and get stuck in that idea. About the wicket-objectsizeof-agent, could it be used to make a small wicket diagnostics contribution..? I mean can it walk over live wicket applications and tell how much individual part were using? Or are some one already doing this? regards Nino Eelco Hillenius wrote: I'm doubting that my wicket application is using to much memory because of serializing too much unnecessary stuff in the session (programmers' mistakes). Can you help me find a way to see what objects get serialized, so I can see what I'm doing wrong and correct my mistakes? Imho the best answer here is: use a profiler, preferably together with load testing (e.g. write a JMeter script). In my experience, it is very hard to make good estimates based on measuring individual objects (note that we even have a separate project for doing slightly more reliable measuring, see https://svn.apache.org/repos/asf/wicket/trunk/jdk-1.5/wicket-objectssizeof-agent) and looking at what the page store saves isn't a good indication for heap usage either. YourKit and JMeter work great for me. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Profiling the memory usage
> I'm doubting that my wicket application is using to much memory because of > serializing too much unnecessary stuff in the session (programmers' > mistakes). Can you help me find a way to see what objects get serialized, so > I can see what I'm doing wrong and correct my mistakes? Imho the best answer here is: use a profiler, preferably together with load testing (e.g. write a JMeter script). In my experience, it is very hard to make good estimates based on measuring individual objects (note that we even have a separate project for doing slightly more reliable measuring, see https://svn.apache.org/repos/asf/wicket/trunk/jdk-1.5/wicket-objectssizeof-agent) and looking at what the page store saves isn't a good indication for heap usage either. YourKit and JMeter work great for me. Eelco - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Profiling the memory usage
also im not sure if the wicket jmx panel could help you here? Nino Saturnino Martinez Vazquez Wael wrote: Look in filepagestore, if youre using the default.. -Nino Stefan Kanev wrote: Hi. I'm doubting that my wicket application is using to much memory because of serializing too much unnecessary stuff in the session (programmers' mistakes). Can you help me find a way to see what objects get serialized, so I can see what I'm doing wrong and correct my mistakes? Thanks in advance. /Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Profiling the memory usage
Look in filepagestore, if youre using the default.. -Nino Stefan Kanev wrote: Hi. I'm doubting that my wicket application is using to much memory because of serializing too much unnecessary stuff in the session (programmers' mistakes). Can you help me find a way to see what objects get serialized, so I can see what I'm doing wrong and correct my mistakes? Thanks in advance. /Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Profiling the memory usage
Hi. I'm doubting that my wicket application is using to much memory because of serializing too much unnecessary stuff in the session (programmers' mistakes). Can you help me find a way to see what objects get serialized, so I can see what I'm doing wrong and correct my mistakes? Thanks in advance. /Stefan
