Re: [Firebird-devel] Memory utilization by Classic Server

[Saulius V. <sa...@gl...>]

Thanks Dmitry. Everything now makes sense. Your formula for lock manager was
missing link.
"ps -e -o size"  - does not include it, while "rss" and "vsize" does.
top "DATA" column also does not include it.

Saulius

> The lock manager data is shared, but it's mapped into the address space
> of the every Classic process. I dunno whether the Linux tools include
> the mmap'ed memory into the counters you check or not. If so, it gets
> easy to explain: yes, this increase is caused by the lock table. You can
> draftly calculate the lock manager memory requirements by this formula:
> <number of connections> * <number of page buffers> * 100 bytes. The
> exact size could be found in the output of fb_lock_print (header
> section) at runtime. With your quite large (for Classic) page cache
> settings, the numbers should be nearly the same as you experience. By
> following Helen's suggestion, you'd save memory both directly (page
> cache) and indirectly (lock table overhead). However, I'm not really
> sure that any action is required, as it's the virtual memory which is
> used in this case, not the physical one (which is used once for all
> processes).
>
>
> Dmitry
>