[MAGNOLIA-6421] evaluate H2 database and replacement derby in the standard bundle Created: 19/Oct/15  Updated: 29/Sep/16  Resolved: 23/Oct/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Philipp Bärfuss Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: pm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLCE-48 Switch default bundle db to H2 Closed
supersession
supersedes MAGNOLIA-6420 Magnolia hangs upon fresh installatio... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Kromeriz 15
Story Points: 2

 Description   

Two good reasons:

  • H2 can run in the VM or externally without bigger changes
  • H2 does not use so many files (see MAGNOLIA-6420)


 Comments   
Comment by Jan Haderka [ 23/Oct/15 ]

Performance is comparable to Derby. See link wiki for details.

Other things to be evaluated: CPU load, Memory usage. Known issues of H2.

Generated at Mon Feb 12 04:14:22 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.