Closed dyudyunov closed 5 months ago
Hi @dyudyunov! Sorry about the long overdue response.
I see that you are sharing nginx access logs, so it means that you are not using Tutor to run Open edX. Is that correct? I also see that your logs are in /edx/var/log/nginx/access.log, which seems to indicate that you are running the native installation -- right?
Still, the response times you are reporting are clearly abnormal. @naumanshafi as the author of the initial implementation of the S3 backend, did you also observe 30s/MB upload times?
I see that you are sharing nginx access logs, so it means that you are not using Tutor to run Open edX. Is that correct? I also see that your logs are in /edx/var/log/nginx/access.log, which seems to indicate that you are running the native installation -- right?
That's correct
@dyudyunov response time depend on the internet upload speed too. Could you please share some stats about you internet upload speed?
@regisb S3 backend implementation @naumanshafi did was for overriding default S3 backend to allow storage and retrieval of content from private S3 bucket. @dyudyunov are you setting this "STORAGE_FUNC": "openedxscorm.storage.s3"
?
@dyudyunov response time depend on the internet upload speed too. Could you please share some stats about you internet upload speed?
This is definitely not the root cause. Tested different people in several locations with several connection options. Here is my speedtest result:
Testing download speed................................................................................
Download: 197.49 Mbit/s
Testing upload speed......................................................................................................
Upload: 78.85 Mbit/s
@dyudyunov are you setting this
"STORAGE_FUNC": "openedxscorm.storage.s3"
?
Yes, no difference
@dyudyunov the issue should not appear again in Quince (tutor v17.0.0). Can you confirm?
@dyudyunov the issue should not appear again in Quince (tutor v17.0.0). Can you confirm?
can't guarantee I can make it till 2024 🙂
I'm not sure I understand -- Quince was released yesterday, and so you should be able to test today. No need to wait until 2024 :)
I meant that I have high-priority tasks to do and I'm not sure I will switch to this one soon)
Right! I did not understand that :sweat_smile: We'll try to do the testing on our side then.
I recently uploaded a SCORM package, sized at 6.2 MB, and it took approximately 67 seconds to complete. My network speeds at the time were as follows: download speed at 14.5 Mbps and upload speed at 18.5 Mbps.
The related PR (https://github.com/overhangio/openedx-scorm-xblock/pull/46) has been closed as won't do, closing the issue as well.
When using the S3 backend for the file storage I discovered that files >1MB are failing to upload.
Backend logs have the 499 error(client closed the connection before response):
The browser request ended up with the 504 (timeout)
After the investigation, I've found that increasing the NGINX timeouts fixes the issue, but it doesn't look like a real solution.
Here are some measurements for my test files (time for the
studio_submit
request to be done):Note: FileSystem storage has no such issues