WebDev 28 Session Memory Usage

I have known for a long time that the longer a user is logged in to my webdev site and the more pages they open and close the more memory the session uses on the server. I have lots of places where I call PageDisplay e.g. on menus and buttons to open other pages. I also load arrays with data which I use to populate loopers on pages. My back button is diabled - all navigation is done via the application i.e. PageDisplays.

I have done lots of controlled tests with two strategies:

a) After every PageDisplay I execute a ContextClose("") - in controlled tests of about 8 different page loads (with large numbers of records in loopers) I am reducing the memory usage by about 37%

b) Before every PageDisplay I execute arraydeletealls of the main looper arrays - in the same controlled tests of about 8 different page loads (with large numbers of records in loopers) I am reducing the memory usage by about 30%

If I do both a and b above then I get a saving of about 40% in memory on the session.

However if I stay logged in and repeat the steps over and over again the memory climbs steadily.

Anyone got any suggestions? What could I do differently? Is there a best practice?

I don't know if it helps but try using PAGEUSE instead of PAGEDISPLAY when possible.

Regards

Paulo Oliveira

Thanks Pao, when I was looking at this issue about a year ago (or more) I tried this. Mostly it worked but often enough I would get crashes that I had to abandon it. Maybe I'll try again if my current "fixes" don't work.

Update on this!


I finally have this working - I have very good savings on memory consumed by the sessions using a combination of deleting class arrays on calling the next page and also doing a ContextClose of previous sessions on page opens. It's taken a LOT of fiddling. It's working well in live in one of my smaller applications. Later this week I'll put it live on my large application where I often have more than a hundred concurrent connections and sessions consuming more than 200mb each! Once I know it's working well I will write it up and pass it on.

Use awb.

the whole purpose of dynamic webdev is sessions

if you ==>ContextClose you loos this. Better use awb and pass params from page to page ands use these to build a context yourself