Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve on veeeery long cold start times #1

Open
rene78 opened this issue May 16, 2019 · 0 comments
Open

Improve on veeeery long cold start times #1

rene78 opened this issue May 16, 2019 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@rene78
Copy link
Owner

rene78 commented May 16, 2019

The cold start time of the functions is around 10s. Definitely not acceptable. Current workaround is to first use copy of portfolio in local storage to display portfolio table and update prices later, if database entry is newer. But this does not take the creation of a new portfolio into account. Thus users have to wait for around 10s, until there new portfolio is saved to the database. Possible ways to mitigate:

  • Implement a "warm-up" function call, when user opens "Create/Edit Portfolio". See this example.
  • Use C# instead of node.js
  • Avoid using npm package "Mongoose", if at all possible
@rene78 rene78 added the enhancement New feature or request label May 16, 2019
@rene78 rene78 self-assigned this May 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant