You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -107,9 +107,6 @@ Windows users may run erigon in 3 possible ways:
107
107
security products for Windows and their respective detection algorythms and we understand this might make your experience with Windows builds uncomfortable. To
108
108
workaround the issue you might either set exlusions for your antivirus specifically for `ethdb\mdbx\dist\CMakeFiles` folder or you can run erigon on Docker or WSL
109
109
110
-
Though is still possible to run erigon with **LMDB** database there's a caveat which might cause your experience with LMDB on Windows uncomfortable: data file allocation is fixed so you need to know in advance how much space you want to allocate for database file using the command line option `--lmdb.mapSize`.
111
-
Please be advised Erigon will completely remove LMDB support in future releases thus we warmly suggest to resync using the default MDBX database.
112
-
113
110
* Use Docker : see [docker-compose.yml](./docker-compose.yml)
114
111
115
112
* Use WSL (Windows Subsystem for Linux) **strictly on version 2**. Under this option you can build Erigon just as you would on a regular Linux distribution. You can point your data also to any of the mounted Windows partitions (eg. `/mnt/c/[...]`, `/mnt/d/[...]` etc) but in such case be advised performance is impacted: this is due to the fact those mount points use `DrvFS` which is a [network file system](#blocks-execution-is-slow-on-cloud-network-drives) and, additionally, MDBX locks the db for exclusive access which implies only one process at a time can access data. This has consequences on the running of `rpcdaemon` which has to be configured as [Remote DB](#for-remote-db) even if it is executed on the very same computer.
@@ -284,9 +281,9 @@ Happy testing! 🥤
284
281
Known issues
285
282
============
286
283
287
-
### `htop` shows incorrect memory usage when using LMDB
284
+
### `htop` shows incorrect memory usage
288
285
289
-
Erigon's internal DB (LMDB) using `MemoryMap` - when OS does manage all `read, write, cache` operations instead of Application
286
+
Erigon's internal DB (MDBX) using `MemoryMap` - when OS does manage all `read, write, cache` operations instead of Application
Copy file name to clipboardExpand all lines: cmd/cons/commands/root.go
-10Lines changed: 0 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,6 @@ import (
14
14
var (
15
15
consensusAddrstring// Address of the consensus engine <host>:<port>
16
16
datadirstring// Path to the working dir
17
-
databasestring// Type of database (lmdb or mdbx)
18
17
configstring// `file:<path>`` to specify config file in file system, `embed:<path>`` to use embedded file, `test` to register test interface and receive config from test driver
19
18
)
20
19
@@ -52,7 +51,6 @@ func must(err error) {
52
51
funcwithDatadir(cmd*cobra.Command) {
53
52
cmd.Flags().StringVar(&datadir, "datadir", paths.DefaultDataDir(), "directory where databases and temporary files are kept")
0 commit comments