Upload Files read timeout (with Persist data) about s3mock HOT 3 CLOSED

@JJRdec
I have an M1 MacBook here and the test case is running without problems:

$ cat docker-compose.yml
services:
  s3mock:
    image: adobe/s3mock:3.1.0
    environment:
      - initialBuckets=bucket1,bucket2
      - root=/data
      - debug=true
      - retainFilesOnExit=true
    ports:
      - 9090:9090
    volumes:
      - ./data:/data
$ docker compose up -d
$ truncate -s 1G output.file
$ aws s3 cp ./output.file s3://bucket1/ --endpoint-url=http://localhost:9090
Completed 1.0 GiB/1.0 GiB (134.0 MiB/s) with 1 file(s) remaining
upload: ./output.file to s3://bucket1/output.file

This took 38s.
Without a mounted volume it takes about half that time.

I see that you're running Docker on Windows.
Unfortunately, volumes are known to be super slow in Windows.
Search the web, many people are complaining about this.

Can't do much here in the short term, I'm afraid.
My advice is to use smaller files for testing, or move to a different operating system.
Docker on Mac introduced VirtioFS which is way faster than the previously available formats.
Supposedly, Docker on Linux is also way faster than Docker on Windows.

At some point, I plan to refactor the way we handle multipart uploads (can't fix #1205 without a refactoring), but I can't say yet if that will speed up the process... Currently we persist every part separately and when the multipart upload is completed, we synchronously write all parts to a new file and delete all parts.
The speed of this operation is highly dependent on the speed of the disk.

from s3mock.

Thanks for the detail around this issue. I see now this is more a docker on windows related issue!

For others on Windows we see two workaround options:

1. Set the read timeout to infinite (only for local develop of course)
2. Use WSL2 and mount a volume on linux subsystem instead on windows.

@afranken I'll leave it up to you if you want to close this issue, thanks!

from s3mock.

@JJRdec sorry I can't do more right now.
I'll close this issue, you should open an issue in the Docker for win repo if you haven't already done so:
https://github.com/docker/for-win
maybe - if enough people ask about it - the Docker team will implement a speed improvement for Windows in the future :)

from s3mock.