On Monday, 3 April 2017 19:34:14 UTC-6, Paul Masson wrote: > > The number of CPUs can't be the direct cause, since the evaluations just > queue up and come back when a CPU is available, right? I can accept that, > but when the evaluations never return it's a problem. > > Of course it is not a reason to stop working, but it is a reason to start being slow even for a single user/page. Now what happens when 10-30-100 students come to a lab and open that page at the same time...
Anyway, I am not telling you that you should stop such usage especially if it tends to work fine. If it does become a major problem then something has to be done on server side to automatically limit the rate of computations for particular users/pages instead of relying on page authors not doing something. Regarding the current problem - what CORS error is happening? We should be good in terms of certificates, they were recently extended. Does the problem relate in any way to how threejs is working now? I've seen NS_ERROR_FAILURE: mentioning threejs files, but didn't understand what exactly is happening. -- You received this message because you are subscribed to the Google Groups "sage-cell" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/dc198c6d-1163-495b-9c92-ea3136a43652%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
