scriptoriumadmin/featurebase
1
0
Fork 0
mirror of https://github.com/featurebasedb/featurebase.git synced 2026-09-09 14:41:02 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #1920 from jaffee/raise-file-map-defaults

Browse source 
increase default max map and file counts [no changelog]
This commit is contained in:
Matthew Jaffee 2019-03-29 18:06:48 -05:00 • committed by GitHub
commit 4f2b757300
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 15 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
docs/configuration.md
View file

@ -127,12 +127,12 @@ The config file is in the [toml format](https://github.com/toml-lang/toml) and h
timestamps will create lots of fragments. When Pilosa exhausts the
max-map-count it falls back to reading files directly into memory. This can be
a bit slower, and cause slower restarts, but is generally fine.
* Flag: `--max-map-count=60000`
* Env: `PILOSA_MAX_MAP_COUNT=60000`
* Flag: `--max-map-count=1000000`
* Env: `PILOSA_MAX_MAP_COUNT=1000000`
* Config:
```toml
max-map-count = 60000
max-map-count = 1000000
```
#### Max Writes Per Request
@ -152,11 +152,11 @@ The config file is in the [toml format](https://github.com/toml-lang/toml) and h
open simultaneously. When past this limit, Pilosa will only keep files open
for as long as it needs to write updates. This will negatively affect
performance in cases where Pilosa is doing lots of small updates.
* Flag: `--max-file-count=500000`
* Env: `PILOSA_MAX_FILE_COUNT=500000`
* Flag: `--max-file-count=1000000`
* Env: `PILOSA_MAX_FILE_COUNT=1000000`
* Config:
```toml
max-file-count = 500000
max-file-count = 1000000
```
#### Gossip Advertise Host

12
server/config.go
View file

@ -143,9 +143,15 @@ func NewConfig() *Config {
DataDir: "~/.pilosa",
Bind: ":10101",
MaxWritesPerRequest: 5000,
MaxMapCount: 60000,
MaxFileCount: 500000,
TLS: TLSConfig{},
// We default these Max File/Map counts very high. This is basically a
// backwards compatibility thing where we don't want to cause different
// behavior for those who had previously set their system limits high,
// and weren't experiencing any bad behavior. Ideally you want these set
// a bit below your system limits.
MaxMapCount: 1000000,
MaxFileCount: 1000000,
TLS: TLSConfig{},
}
// Cluster config.