Project

General

Profile

Feature #1851

database performance/scalability tuning

Added by Eric Faulhaber over 11 years ago. Updated over 7 years ago.

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

0%

Estimated time:
240.00 h
billable:
No
vendor_id:
GCD

Related issues

Related to Database - Bug #3031: FOR EACH can access shared transient records in case of broken transaction isolation New

History

#1 Updated by Eric Faulhaber over 11 years ago

This is a parent issue to which to add more granular tasks regarding performance and scalability tuning of the P2J persistence conversion tools and runtime framework.

Starting ideas (not a complete list):
  • more granular/better 2nd level cache (especially on read-only tables)
  • make adaptive query support multi-table (currently, all non-preselect, multi-table queries are converted to CompoundQuery, which is relatively slow)

#2 Updated by Greg Shah over 11 years ago

  • Target version set to Milestone 17

#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