In article <32844747.22509345@www.weideneder.de>, Stefan Weideneder
<stefan@www.weideneder.de> writes
>
>What I know is, that Informix has two different memory management
>routines in the OnLine Server. The one which manages the virtual
>portion ( 8KB blocks ) and another one for the prepared SQL-statements
>and cursors, called ralloc() ( this function used 1096 Byte blocks in
>earlier versions ). Once you prepare a statement, the memory will be
>allocated inside the virtual portion. From now on this memory can only
>be used by the session which allocated the memory, even if the session
>frees the prepared statement id. This means, if you prepare a lot of
>different statements at the beginning of your application, you can see
>the growth of the ralloc() pool with "onstat -g ses ##". If you don't
>need the memory any more, and now try to free the prepared statements
>or cursors, this memory can't be reused by other sessions. Depending on
>the kind of programming this could cause a memory problem inside the
>server.
Interesting - how did you find this out?.
--
David Williams