Subject | Re: [firebird-support] Connection overhead |
---|---|
Author | Daniel Rail |
Post date | 2004-12-18T14:38:17Z |
Hi,
At December 17, 2004, 20:38, Chad Z. Hower wrote:
just waiting until security.fdb is loaded in memory. And IIRC,
security.fdb is supposed to stay in memory until there is no more
connections to Firebird. With Classic, it could be different, since
every connection is a separate process, and that each process loads
its own copy of security.fdb.
But, I didn't find any problems without connection pooling when using
Intraweb and a good amount of concurrent and/or rapid sequential
connections. The best way to find out is to do your own load testing.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)
At December 17, 2004, 20:38, Chad Z. Hower wrote:
> :: Well, perhaps you answered your own question if you alreadyWith FB 1.5 SS, maybe the first connection might have a slight delay,
> :: understood the benefit of pooling.
> I fully understand the benefit. But Im in a situation in which pooling is
> causing some undesirable side effects and so I need to provide a tangible
> measurement as to the benefit specific to using pooling with *FB* in this
> scenrio.
just waiting until security.fdb is loaded in memory. And IIRC,
security.fdb is supposed to stay in memory until there is no more
connections to Firebird. With Classic, it could be different, since
every connection is a separate process, and that each process loads
its own copy of security.fdb.
But, I didn't find any problems without connection pooling when using
Intraweb and a good amount of concurrent and/or rapid sequential
connections. The best way to find out is to do your own load testing.
--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)