On 21 September 2013 09:05, Sergio Boso <[email protected]> wrote: > just to add some info, you have to take in account that Jmeter keeps all the > sample's result in memory, even i there is no further process for it.
Half true. Samplers store the full response unconditionally in memory (except if MD5 hash is selected), regardless of whether there are any other test elements that need to use the data. However this is temporary - JMeter only _keeps_ the result in memory if it is still needed. For example, the Tree View and Table Listeners display individual samples, so they keep all sample results. And in non-GUI mode, since there are no displays, even the Tree View Listener does not store thre results. > So, if you are downloading some large objects (like imaging, SW updates and > so on), then you can easily go out of memory. > > If this is the case, look for the maximum object size run just few threads > and increase memory accordingly (HEAP option, in Jmeter start script) > > HTH > > Sergio > > > > Il 20/09/2013 08.02, bobMeliev ha scritto: > >> When you get this error a file with extension .hprof gets created. This is >> the heap dump created when the JVM crashed. This file can be analysed >> using >> Heap Analysis tools to identify the root cause. Ex: You can try analysing >> using JHAT ( >> http://docs.oracle.com/javase/6/docs/technotes/tools/share/jhat.html ) >> >> >> >> -- >> View this message in context: >> http://jmeter.512774.n5.nabble.com/jmeter-memory-leak-tp4938431p5718206.html >> Sent from the JMeter - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > -- > > Ing. Sergio Boso > > > > > > --------------------------------------------------------------------- > 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]
