> > Allan,
> >
> > > Server example as a snapshot today with 12 simultaneous connections:
> > > Task Manager:
> > > Mem Usage: 114,528K
> > > Peak Mem Usage: 185,344K
> > > VM Size: 159,816K
> > >
> > > isc_database_info() returns
> > > CurrentMemory: 68,881K
> > > MaxMemory: 116,125K
> > >
> > > New connections add another approx 2Mb of RAM usage and when they
> > > disconnect the ram drops back - I can reliably observe the recovery
> > in ram
> > > usage.
> > >
> > > I am trying to find why over the last couple of days I have
> > experienced
> > > (twice) a case of an exception (cannot allocate memory from OS) where
> > the
> > > server MemUsage in Task manager was reporting over 1Gb of ram and
> > > connections were being refused.
> >
> > What value were you looking at to see that 1GB of RAM was free?
> >
> > How much physical RAM is in the server?
> >
> > What OS is the server running?
> >
> >
> > Sean
>
> Mem Use was over 1Gb for fbserver.exe process
> Server OS is Windows Server 2003
> It has 2Gb RAM with 2062Mb of virual memory
> At the bottom of task manager at the time, the Commit Charge was 50%, ie.
> about <2Gb / 3959M
> Since I have stopped monitoring the fbserver.exe process has not exceeded
> 241Mb (peak Mem Usage) and Mem Usage if frequently about 80Mb.

Firebird like many applications requires PHYSICAL memory to be available, not virtual memory. So, the errors are because the server ran out of available physical RAM. (The commit charge value represents available virtual memory)


Sean