On 9/23/2010 11:42 AM, zhu qun-ying wrote:
Hi,
I have an SSL apllication, that it suppose to run for a long time. After some
time of running, I found the usage of the memory is growing. I stop all SSL
connections and checked all SSL * has been freed but it could not release the
memory back to the system.
After some investigation, I found there is no memory leak, but seems lot of
memory are unable to release back to system. mtrace found out there are quite
a lot of fragmented memory being held by the SSL library. I would like to know
what could I do to reduce the memory held by SSL library after all connections
have been dropped?
I am handling the SSL session through share memory myself and that part of the
memory is allocated from the start.
mallinfo() reports after some test and no connection for a while:
system bytes = 28271952
in use bytes = 1809184
non-inuse bytes = 26462768
non-inuse chunks = 81
mmap regions = 4
mmap bytes = 1773568
Total (incl. mmap):
system bytes = 30045520
in use bytes = 3582752
releasable bytes = 462496
--
qun-ying
This all seems normal. Virtual memory is not normally considered a
scarce resource and unless the consumption is really absurd, it's not
worth worrying about.
Unless your virtual memory use grows linearly with constant load, it's
generally not worth worrying about. If it grows in an exponentially
decreasing way with constant load or grows linearly with increasing peak
load, I wouldn't worry about it at all.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
