Project

General

Profile

Feature #3011

try H2 internal connection pool instead of UnpooledConnectionProvider

Added by Eric Faulhaber almost 8 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD

History

#1 Updated by Eric Faulhaber almost 8 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 over 7 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 over 7 years ago

  • Target version changed from Milestone 17 to Performance and Scalability Improvements

Also available in: Atom PDF