[DERBY-4210] Use a shared pool for background threads (rawStoreDaemon)

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.5.1.1
• Component/s: Store
• Assignee: Unassigned
• Reporter: Arnaud Masson
• Created: 04/May/09 09:09
• Updated: 08/Dec/09 18:24

Description

Use a shared pool for background threads (rawStoreDaemon).
May it could be a configuration option (pooling or not, max pool size, core pool size, ...).

I have an application that opens several small derby databases (using EmbeddedDriver).
Most of these instances don't handle many requests, but each instance maintains its own thread "derby.rawStoreDaemon".
It would more efficient to use a thread pool shared by all the instances.

See http://osdir.com/ml/apache.db.derby.devel/2005-04/msg00093.html
See also DERBY-206 and DERBY-696 about threading in Derby.

Issue Links

• is related to: DERBY-696 Use the Executor framework to spawn off client threads in the NetworkServer
• is related to: DERBY-206 To conserve resources, Network Server could clean up connection threads that are not used for a long period of time