In article <339D9793.7A48@eds.com>,
Greg Moye <msmcl301.gmoye01@eds.com> wrote:
>We have a nice, simple two tier application, with a Powerbuilder based
>client connecting to a V7.13 engine. New connections start out using
>very little memory (virtual pool I think) as reported by "onstat -g
>ses". Then over time it increases, some getting as high at 20+
>megabytes. Usage is mostly OLTP, some light reporting also.
>
>Anybody have a clear understanding of what kind of client activity uses
>this memory over time (it seems to be freed up when the session is
>terminated)??
>
We use I4gl applications.
We've never hit 20+ Mb! Our sessions' usage of memory would gradually
go up, stablizing at about 1.2Mb in some cases. In our attempt to
reduce the memory usage, the following helped
1. FREE PREPARED statements when they aren't required (FREE stmt_q1)
2. CLOSE & FREE CURSORS when they aren't reqd.
(CLOSE narr_curs; FREE narr_curs)
3. If possible, for printing use 'RUN fglgo print4go args'. Printing
will be slower, but memory usage could be better.
4. Knock off users who are idle (if possible :-))
Items 1 and 2 caused a reduction in usage of about 25-40% in our case.
Obviously, this will depend on your programs stmts.
HTH.
----------------------------------------------
Rudy Fernandes
Frying Pan to the Freezer : Kuwait to Toronto
----------------------------------------------