Feature #3011
try H2 internal connection pool instead of UnpooledConnectionProvider
Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Performance
History
#1 Updated by Eric Faulhaber over 10 years ago
I read in the H2 documentation that the H2 internal connection pool should be significantly faster for embedded databases than using the DriverManager directly, which is what UnpooledConnectionProvider does. I'm not sure if this also applies to in-memory databases, but it's probably worth a try -- the effort to implement this is not high.
#2 Updated by Eric Faulhaber about 10 years ago
- Status changed from New to Rejected
Tried this. It went very badly. We need to maintain the existing mechanism of holding open connections for as long as any temp table exists.
#3 Updated by Greg Shah almost 10 years ago
- Target version changed from Milestone 17 to Performance and Scalability Improvements
#4 Updated by Eric Faulhaber 16 days ago
- topics Performance added
Adding performance topic for posterity, even though this was rejected.