[PR #1922] [MERGED] Enable noobj_cache by default #2257

New issue

Closed

opened 2026-03-04 02:04:36 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 02:04:36 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/1922
Author: @gaul
Created: 3/11/2022
Status: ✅ Merged
Merged: 3/12/2022
Merged by: @ggtakec

Base: master ← Head: noobj-cache

📝 Commits (1)

203cb70 Enable noobj_cache by default

📊 Changes

6 files changed (+17 additions, -17 deletions)

View changed files

📝 doc/man/s3fs.1.in (+4 -5)
📝 src/cache.cpp (+1 -1)
📝 src/s3fs.cpp (+5 -0)
📝 src/s3fs_help.cpp (+5 -9)
📝 test/integration-test-main.sh (+1 -1)
📝 test/small-integration-test.sh (+1 -1)

📄 Description

This should improve performance in many situations. s3fs already
enables the stat cache by default so memorizing noobj makes this more
consistent. Fixes #1901.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/s3fs-fuse/s3fs-fuse/pull/1922 **Author:** [@gaul](https://github.com/gaul) **Created:** 3/11/2022 **Status:** ✅ Merged **Merged:** 3/12/2022 **Merged by:** [@ggtakec](https://github.com/ggtakec) **Base:** `master` ← **Head:** `noobj-cache` --- ### 📝 Commits (1) - [`203cb70`](https://github.com/s3fs-fuse/s3fs-fuse/commit/203cb70f39c3dfb9aaa78ba96975e0fb28cc250c) Enable noobj_cache by default ### 📊 Changes **6 files changed** (+17 additions, -17 deletions) <details> <summary>View changed files</summary> 📝 `doc/man/s3fs.1.in` (+4 -5) 📝 `src/cache.cpp` (+1 -1) 📝 `src/s3fs.cpp` (+5 -0) 📝 `src/s3fs_help.cpp` (+5 -9) 📝 `test/integration-test-main.sh` (+1 -1) 📝 `test/small-integration-test.sh` (+1 -1) </details> ### 📄 Description This should improve performance in many situations. s3fs already enables the stat cache by default so memorizing noobj makes this more consistent. Fixes #1901. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>