2012/3/18 Mark Rotteveel m...@lawinegevaar.nl
> The working set size is the amount of memory currently paged into
> physical memory, not the total (virtual) memory size of a process (see
>
> http://msdn.microsoft.com/en-us/library/windows/desktop/cc441804%28v=vs.85%29.aspx
> )
>
> If Firebird is not accessing certain memory pages, Windows is free to
> reduce the working set and store those memory pages in the pagefile.
>
The issue (i thnk) is that:
1. Firebird max memory allocated is more than max memory used
2. After windows unload pages from working set and has a minimum working
set for one database connection, when the connection is used again, the
working set is equal (more or less) than the really max memory used, and
never the max memory allocated, may be because the difference between max
memory allocated and used is not needed again and is stored in the page
file.
The question is if in any internal process of firebird does not free or
allocate more memory than needed and that causes that one connection
uses more 120MB of RAM. If from that 120MB, the really memory used is 60MB,
the working set needed to load all process' memory is 60MB instead of
120MB, and the memory needed for each connection is less.
Jesus
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
