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

Update to server pool use #12

Merged
merged 1 commit into from
Apr 4, 2022
Merged

Update to server pool use #12

merged 1 commit into from
Apr 4, 2022

Conversation

HarikalarKutusu
Copy link
Owner

This PR implements a mini-server-pool that we talked about in #4 as the second option.

We also created four such servers on free Heroku accounts, to be able to open a test site. We expose the server names for you to work on the client with multiple servers (via npm run start:remote which uses localhost for client and remote server pool for chess STT inference). As these servers are on free accounts, they most probably be in sleep mode, so it will take a couple of seconds until they wake up, so put a 3x connection trial and a timeout of 5 sec.

It basically starts with the first server and tries to connect. If the server is full, it loops through the server pool until an empty one is found. Each server continues to host a single session.

@HarikalarKutusu HarikalarKutusu added enhancement New feature or request backend Server related frontend Client related labels Apr 4, 2022
@HarikalarKutusu HarikalarKutusu merged commit 7d5e84f into main Apr 4, 2022
@HarikalarKutusu HarikalarKutusu deleted the feature/server-pool branch April 4, 2022 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Server related enhancement New feature or request frontend Client related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant