EDC - Faster Startup

[lgblaumeiser]

Description

We have the requirement to start the EDC as fast as possible to fulfill our internal requirements. With the following resource specs, the EDC needs around 40-50 seconds to start, and we don’t want to give him more Cores because most of the time he is idling around which would be then a waste of resources: CPU: 1 Core (AMD EPYC 7763), RAM: 3 GB.

Requestor: @florianrusch-zf

Impact

No impact on external dependencies as this is a technical issue during startup. No behavior change to the outside world except for faster availability.

[lgblaumeiser]

Discussion in weekly today:

• Multiple aspects, like, e.g., database connection setup
• Depends on the EDC configuration
• Concrete goals are missing, what is acceptable

Proposal: Get more into details of what is expected and which approaches there are concerning optimization

[lgblaumeiser]

Transfered Comment from @jimmarino 1392

@florianrusch-zf 40-50 seconds? Wow, that is a lot. Please take a look at your distribution configuration. Is it making many remote calls? EDC is designed to (and does) boot in milliseconds. This was an explicit design goal with the runtime boot subsystem - that's one of the reasons why it does not use classpath scanning or complex DI frameworks.

My guess is the issue is with remote startup calls.

[stephanbcbauer]

Presented in the DRAFT Feature Freeze -> Committer is available

[lgblaumeiser]

De-Prioritized, no work planned for 24/12