-
Notifications
You must be signed in to change notification settings - Fork 192
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.
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
[LibOS] experimental flock significantly increases file size #1811
Comments
Looking at the PR that introduced Can you debug a bit more:
|
After doing some more digging, this seems to be related to a regression in gramine's tmpfs implementation rather than flock. The increased file size is not observable when running gramine 1.5, whereas gramine +1.6 uses up significiant more space compared to the folder on disk. Copying a folder containing a huge amount of files <=2MB which amounts to ~280GB of size into tmpfs, even with enclave_size=1024GB results in OOM. See attachment chaindata.txt for folder structure. |
The only commit I can see since 1.5 which I think could influence this could be 1ea3e60, assuming it introduces some memory leak. I didn't see anything other related to tmpfs, but maybe I just missed something... Could you check if this is the commit causing the regression? |
@lead4good Any progress on debugging this? I don't see anything special in the 1ea3e60 commit. I also don't understand how tmpfs (which uses buffers in enclave memory) relates to the file sizes in database folders. Or do I misunderstand your application and which files exactly are increased in size? |
Description of the problem
Running go-ethereum in Gramine with experimental flock support we experience an increase of file size (300-1000%) compared to not setting the flock for the database folders.
Steps to reproduce
No response
Expected results
No response
Actual results
No response
Gramine commit hash
v1.6
The text was updated successfully, but these errors were encountered: