[FINERACT-1439] Performance hammered by too many EAGER Load

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Ed Cable
• Reporter: James Dailey
• Created: 09/Nov/21 21:01
• Updated: 09/Nov/21 21:14

Description

Putting this in JIRA now to emphasize a pattern we need to avoid and to call for some PRs to correct some issues recently introduced into dev branch. We should use Eager load in SQL very very infrequently. Use lazy loading to avoid the hit to performance. Get only what you need, when you need it.

Eager loading retrieves the full model and relational data. In a complex data model like fineract, that means loading dozens of tables data that you won't use in your operation. That is a pattern we must avoid to keep the platform scalable.

We need to not only tune (see https://issues.apache.org/jira/browse/FINERACT-912) but to set up tests to avoid creating new problems as features are added. I think the tests need to exercise each API and get a response back within a predetermined timeframe.

Doing the right SQL statements is harder, but more rewarding!!

Issue Links

• incorporates: FINERACT-912 Tune JPA Eager/Lazy loading for performance