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

[CDI-CAT] scope of work to move from separately-hosted plumbr API to jsCAT #528

Open
kachergis opened this issue Jun 27, 2024 · 1 comment
Assignees

Comments

@kachergis
Copy link
Member

Some users recently had issues with the CAT API crashing, apparently due to hitting a memory limit on the server. While the server size can be increased, hosting costs correspondingly increase.* As we release more CATs, demand will only increase, and could peak unpredictably. Given that there are client-side options for running CATs**, we would like to know how heavy it would be to migrate away from plumbr.

  • @HenryMehta , more context for this decision would be helpful: from the logs, do you know how many users it took to crash the small server? What is the monthly cost of a small vs. medium server?

** e.g. https://yeatmanlab.github.io/jsCAT/

@HenryMehta
Copy link
Collaborator

I have very very basic log data with CAT. Basically, what is the state of the server. I have no idea of the number of participants which caused the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants