>> -----Original Message-----
>> From: Vlad Khorsun [mailto:[email protected]]
>> Sent: Lunes, 09 de Mayo de 2011 6:07
> ....
>> To avoid contention on common dbb_pool its usage was
>> replaced by att_pool when
>> possible. To make this task slightly easy there was
>> introduced jrd_rel::rel_pool which
>> is points currenlty to the attachment's pool. All relation's
>> "sub-objects" (such as
>> formats, fields, etc) is allocated using rel_pool (it was
>> dbb_pool before). When we'll
>> return metadata objects back to the Database it will be easy
>> to redirect rel_pool to
>> dbb_pool at one place in code instead of makeing tens of
>> small changes again.
>
> And the statistics about memory usage in the engine, do they return the same
> values as before?
It shouldn't be changed because of this. To be true - i don't know, and
even not sure we have correct memory statistics currently. It should be
checked separately.
Regards,
Vlad
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
