BorlandTalk.com

Sean Gifford · Guest

I'm not sure if this is the right place for this question, but I'll ask
it here because it is affecting our server....

We have a D6 SvCOM service with one parent and two child RDM. Our
connection to our MSSQL 2000 DB is via the latest CoreLab DBExpress
driver. We're running on Windows 2000 and XP, and we're using the
performance monitor for our memory observations.

We see the memory attributed to our server rise drastically on the first
connection. This makes sense, as this is when the server first sets up
and loads the OLE driver, the DBExpress driver, Midas.dll, etc. It
seems that each opened table will cause a bit of a rise, until a
plateau, after which the memory use stays relatively constant. Each
additional connection will cause a sharper rise in memory used, but that
is regained when that connection is closed, returning to the first
plateau.

The mystifying part is when we experiment with a standard executable
server. It exhibits the same behaviour, except that when the main form
is minimized, the working set drops down to close where it was before
the first connection. This amounts to a huge drop in memory use. The
private bytes for the app stay fixed at their plateau, which until the
main form was minimized was significantly less than the working set plateau.

What's going on? Is there anything we can do to force this memory
reclamation? If the memory is allowed to stay at its high level, is
this going to adversely affect other applications on the machine?

Thanks in advance for any comments!