Hello,
I am running an Internxt environment on a Synology NAS. After upgrading the Docker container from internxt-cli 1.6.2 to 1.6.4, I started experiencing major stability issues with Synology HyperBackup, along with a significant performance degradation.
To isolate the problem, I developed a small Java program using Sardine to interact directly with the WebDAV interface, bypassing HyperBackup entirely.
The results clearly show that version 1.6.4 is significantly slower than 1.6.2 under identical conditions.
Environment
- Device: Synology NAS
- Deployment: Docker container
- Network: ~50 Mbps upload
- Client: custom Java program using Sardine (WebDAV)
Test setup
- 99 files
- no pictures
- Total size: 274 MB
- Identical dataset and environment for both versions
- Target directory is always empty before each test
Important detail
Before each upload, the client performs a WebDAV PROPFIND request to check whether the file already exists.
Since the directory is empty, this request always returns no results, eliminating:
- Cache effects
- Overwrite scenarios
- Large directory listing overhead
Results
internxt-cli 1.6.4
- Total transfer time: 1194 s (~3.8× slower than 1.6.2)
WebDAV timings:
- PROPFIND average: 4314 ms
- PUT average: 7702 ms
internxt-cli 1.6.2
- Total transfer time: 317 s
WebDAV timings:
- PROPFIND average: 484 ms
- PUT average: 2552 ms
Analysis
- PROPFIND requests are ~9× slower in 1.6.4
- PUT requests are ~3× slower in 1.6.4
- Overall performance degradation is ~4×
This strongly suggests a WebDAV regression introduced in version 1.6.4.
Request
Could you please investigate this regression in WebDAV performance between internxt-cli 1.6.2 and 1.6.4?
Given the consistent and significant slowdown observed in both PROPFIND and PUT operations, this appears to be a performance regression introduced in 1.6.4 (or 1.6.3).
Hello,
I am running an Internxt environment on a Synology NAS. After upgrading the Docker container from internxt-cli 1.6.2 to 1.6.4, I started experiencing major stability issues with Synology HyperBackup, along with a significant performance degradation.
To isolate the problem, I developed a small Java program using Sardine to interact directly with the WebDAV interface, bypassing HyperBackup entirely.
The results clearly show that version 1.6.4 is significantly slower than 1.6.2 under identical conditions.
Environment
Test setup
Important detail
Before each upload, the client performs a WebDAV PROPFIND request to check whether the file already exists.
Since the directory is empty, this request always returns no results, eliminating:
Results
internxt-cli 1.6.4
WebDAV timings:
internxt-cli 1.6.2
WebDAV timings:
Analysis
This strongly suggests a WebDAV regression introduced in version 1.6.4.
Request
Could you please investigate this regression in WebDAV performance between internxt-cli 1.6.2 and 1.6.4?
Given the consistent and significant slowdown observed in both PROPFIND and PUT operations, this appears to be a performance regression introduced in 1.6.4 (or 1.6.3).