xuang7 opened a new issue, #4051:
URL: https://github.com/apache/texera/issues/4051
### What happened?
The elapsed “upload time” displayed for uploads includes the initialization
time (time spent waiting, signing URLs, etc.) instead of only the actual upload
time.
**Example scenario: (network adjusted mid-upload)**
- File 2GB.txt starts uploading
- File 1GB.txt remains queued while init/URL presigning takes ~45s due to
poor network conditions
**Expected behavior:** At the moment File 1GB.txt starts uploading, its
elapsed time should show 0s (count only data transfer).
**Actual behavior:** When File 1GB.txt begins uploading, the timer already
shows ~45s (init/presign time included).
https://github.com/user-attachments/assets/13089992-4f4b-4df4-92f4-36e90d7dc997
**Likely cause**: startTime is set when the Observable is created rather
than when the first PUT (or first progress event) starts, so initialization
time is counted as upload time.
### How to reproduce?
1. Upload few large files at once.
2. Wait a bit.
- Under limited resources/network, one file begins uploading while another
sits in init/presign, its elapsed time includes the initialization period.
- Alternative: In DevTools, throttle the network to simulate limited
resources. The file’s “upload time” increases during init/presign (before the
first PUT), so when the upload actually starts it already shows elapsed time.
### Version
1.1.0-incubating (Pre-release/Master)
### Commit Hash (Optional)
_No response_
### What browsers are you seeing the problem on?
Chrome
### Relevant log output
```shell
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
