Closed sampaccoud closed 3 years ago
I think your analysis of the problem is correct @sampaccoud. Can you just specify which version of the xblock you are running?
EDIT: do you have an opinion on whether it's really useful to store the zip file on S3? My feeling is that we could get rid of it entirely.
We are running openedx-scorm-xblock==9.2.5
on Ironwood.
Yes, we also feel that the zip file should be trashed after being unzipped...
Solved in v10.1.0 and v9.3.0.
Our users reported timeouts when uploading Scorm modules. We had to drastically increase timeouts on our web servers to solve the issue but, digging a little bit, we think uploads are abnormally slow.
On first glance, the sequence of events happening while the user is holding the request is:
This seems far too many things to do while holding on a user request. It could be improved:
or
Even more efficient would be to upload directly to S3 with an upload policy... and the unzipping could be done directly in S3 via a lambda trigger but it would not work for alternative S3 hosting, swift, etc. so I think the two first solutions are better for the OpenEdX community.