I have been trying to get a handle on the ways in which RAM is utilized on the WAS. I have previously reported problems with RAM creeping up over the course of a day. It has led me to have to restart the server several times per day.
Session variables do seem to drain RAM, and simply deleting them or even using session.reset() does NOT reclaim the memory used. Boy, I wish this was pointed out before investing so much time in creating an application. I have had to make many changes after the fact - and it does improve RAM usage and performance.
HOWEVER - I have discovered that the biggest drain on RAM, at least for me, is in the use of reports! To illustrate, I have restarted the WAS, logged in to my application and am now at a page from which I will run a relatively simple report. RAM is now at 70,480K. I now click submit to run the report, and the PDF opens on my display - RAM is now at 82,004K. WOW - 11.5MB just to run and display one relatively simple report. Closing the report by using the browser back button, and even logging out of the application brings RAM down to 75,706K: 5,226K of RAM was NOT recovered. And this is just for one report and one user!
I have now logged back in, and am back at the same screen to generate that same report again. RAM is at 75,512K. I run the report again, and then again use browser back button to close the report. RAM is now at 75,556K. Pretty much back to wehere we were after the first run of the report. But still missing approc 5,000K of RAM.
Ran another report and closed it. RAM is now at 77,564K - another 2,000K of RAM is lost!
Can anyone make sense out of this for me. And more importantly, is there a way to recover ALL of the RAM that is used by reports.
Session variables do seem to drain RAM, and simply deleting them or even using session.reset() does NOT reclaim the memory used. Boy, I wish this was pointed out before investing so much time in creating an application. I have had to make many changes after the fact - and it does improve RAM usage and performance.
HOWEVER - I have discovered that the biggest drain on RAM, at least for me, is in the use of reports! To illustrate, I have restarted the WAS, logged in to my application and am now at a page from which I will run a relatively simple report. RAM is now at 70,480K. I now click submit to run the report, and the PDF opens on my display - RAM is now at 82,004K. WOW - 11.5MB just to run and display one relatively simple report. Closing the report by using the browser back button, and even logging out of the application brings RAM down to 75,706K: 5,226K of RAM was NOT recovered. And this is just for one report and one user!
I have now logged back in, and am back at the same screen to generate that same report again. RAM is at 75,512K. I run the report again, and then again use browser back button to close the report. RAM is now at 75,556K. Pretty much back to wehere we were after the first run of the report. But still missing approc 5,000K of RAM.
Ran another report and closed it. RAM is now at 77,564K - another 2,000K of RAM is lost!
Can anyone make sense out of this for me. And more importantly, is there a way to recover ALL of the RAM that is used by reports.
Comment