noReadAhead option, CLOEXEC the LMDB file

This commit is contained in:
Doug Hoyte
2023-08-10 16:33:18 -04:00
parent 206b14a473
commit 276b243ffd
4 changed files with 8 additions and 2 deletions

1
TODO
View File

@ -28,4 +28,3 @@ rate limits (maybe not needed now that we have plugins?)
misc
? periodic reaping of disconnected sockets (maybe autoping is doing this already)
? why isn't the LMDB mapping CLOEXEC

2
golpe

Submodule golpe updated: 67830690a6...8d21667dd0

View File

@ -115,6 +115,10 @@ config:
desc: "Size of mmap() to use when loading LMDB (default is 10TB, does *not* correspond to disk-space used)"
default: 10995116277760
noReload: true
- name: dbParams__noReadAhead
desc: "Disables read-ahead when accessing the LMDB mapping. Reduces IO activity when DB size is larger than RAM."
default: false
noReload: true
- name: events__maxEventSize
desc: "Maximum size of normalised JSON, in bytes"

View File

@ -11,6 +11,9 @@ dbParams {
# Size of mmap() to use when loading LMDB (default is 10TB, does *not* correspond to disk-space used) (restart required)
mapsize = 10995116277760
# Disables read-ahead when accessing the LMDB mapping. Reduces IO activity when DB size is larger than RAM. (restart required)
noReadAhead = true
}
events {