Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Running out of heap space for large files #922

Closed
jakelamotta opened this issue Nov 21, 2022 · 2 comments · Fixed by #926
Closed

Running out of heap space for large files #922

jakelamotta opened this issue Nov 21, 2022 · 2 comments · Fixed by #926
Assignees
@afranken
Labels
feature

Comments

@jakelamotta
Copy link

Is it possible to configure the container to run with a larger max heapspace than the current 128Mb? I am running the 2.8.0 version of the S3Mock.
@afranken afranken self-assigned this Nov 21, 2022
afranken added a commit that referenced this issue Nov 21, 2022
@afranken
Let JVM use available Docker resources
84b74c8 
If needed, cpu and memory limits can be set for the container, the JVM
will adjust automatically.

Fixes #922
@afranken afranken mentioned this issue Nov 21, 2022
Merged
2 tasks
afranken added a commit that referenced this issue Nov 22, 2022
@afranken
Let JVM use available Docker resources
0d77cdb 
If needed, cpu and memory limits can be set for the container, the JVM
will adjust automatically.

Fixes #922
afranken added a commit that referenced this issue Nov 22, 2022
@afranken
Let JVM use available Docker resources
3641474 
If needed, cpu and memory limits can be set for the container, the JVM
will adjust automatically.

Fixes #922
afranken added a commit that referenced this issue Nov 22, 2022
@afranken
Let JVM use available Docker resources
03b3fab 
If needed, cpu and memory limits can be set for the container, the JVM
will adjust automatically.

Fixes #922
@afranken
Copy link
Member

Just released 2.10.0, now S3Mock uses the resources available to the container.
The JVM will automatically use 50% of the available memory.

If you wanted to give 1GB to the S3Mock, you'd have to run --memory="2g".

@Neoclassic Neoclassic mentioned this issue Nov 24, 2022
Closed
@afranken afranken mentioned this issue Nov 24, 2022
Closed
@afranken
Copy link
Member

Also, I just released 2.10.1 which fixes a bug where incoming request bodies would be read fully into memory.
With 2.10.1, I am able to persist large files (multiple GBs) when running S3Mock with a 64MB heap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afranken afranken

Labels
feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Let JVM use available Docker resources adobe/S3Mock
2 participants
@afranken @jakelamotta