You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For large files, memory upload consumes significant memory and it grows even more when writing out the file iobuffer.
Upload is very slow and consumes significant CPU when everything is on the same host (both reflex and the browser). Uploading files shouldn't really consume much CPU at all...
To Reproduce
Steps to reproduce the behavior:
Just use the standard upload example and upload a multi-gigabyte file.
Expected behavior
Very little memory should be used because the data should be incrementally written to a file.
To avoid re-writing the file after upload, I'd expect to be able to specify the target or if you choose to write to a temporary file I'd expect to be able to rename the temporary file to it's final home.
Specifics (please complete the following information):
Another odd behavior for upload is the on_upload_progress which claims the upload is 100% done but then spends another 10% of the time before returning from rx.upload_files and passing the result on to the handle_upload function.
Describe the bug
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Very little memory should be used because the data should be incrementally written to a file.
To avoid re-writing the file after upload, I'd expect to be able to specify the target or if you choose to write to a temporary file I'd expect to be able to rename the temporary file to it's final home.
Specifics (please complete the following information):
The text was updated successfully, but these errors were encountered: