epam / epam/cloud-pipeline

Review the API startup process performance

Open
#995 1 comment 0 reactions 2 assignees Claimed by @kamyshova View on GitHub
kind/enhancement sys/core
Dominant language
Java
Stars
163
Forks
65
Avg merge
11h 46m
Merged PRs (30d)
29

Description

**Background**
From time to time we need to reboot the API service (e.g. to perform an update). In the production environment the timings a critical.
At the moment, it takes ~90s from the java process start, till the API/GUI become available to the users.
It would be great to minimize this time to whatever possible value.

**Approach**
* If there are any options, that allow to "just reduce time" - that would be great
* As the goal is to expose API/GUI as soon as possible - it is ok to keep the overall initialization process timings, but start the HTTP server earlier to make the GUI available before other system daemons.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.