langcog/web-cdi

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

Opened this issue · 1 comments

kachergis commented

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 commented

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.