mirror/erigon-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2024-12-22 03:30:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

fixed some typos (#5158)

Browse Source
This commit is contained in:
Alireza Arjmand 2022-08-23 20:52:31 -06:00 committed by GitHub
parent 9d3b3ffccc
commit 8a5ceb7def
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -169,7 +169,7 @@ C:\ProgramData\chocolatey\lib\mingw\tools\install\mingw64\bin
During MinGW's compiler detection phase some temporary executables are generated to test compiler capabilities. It's
been reported some anti-virus programs detect those files as possibly infected by `Win64/Kryptic.CIS` trojan horse (or
a variant of it). Although those are false positives we have no control over 100+ vendors of security products for
Windows and their respective detection algorythms and we understand this might make your experience with Windows
Windows and their respective detection algorithms and we understand this might make your experience with Windows
builds uncomfortable. To workaround the issue you might either set exclusions for your antivirus specifically
for `build\bin\mdbx\CMakeFiles` sub-folder of the cloned repo or you can run erigon using the following other two
options
@ -415,7 +415,7 @@ make docker-compose
# if you followed above instructions
#
# Note: uid/gid syntax below will automatically use uid/gid of running user so this syntax
# is intended to be ran via the dedicated user setup earlier
# is intended to be run via the dedicated user setup earlier
#
DOCKER_UID=$(id -u) DOCKER_GID=$(id -g) XDG_DATA_HOME=/preferred/data/folder DOCKER_BUILDKIT=1 COMPOSE_DOCKER_CLI_BUILD=1 make docker-compose
@ -550,7 +550,7 @@ Send an email to `security [at] torquem.ch`.
### Team
Core contributors (in alpabetical order of first names):
Core contributors (in alphabetical order of first names):
* Alex Sharov ([AskAlexSharov](https://twitter.com/AskAlexSharov))
@ -578,7 +578,7 @@ Thanks to:
* All contributors of Go-Ethereum
* Our special respect and graditude is to the core team of [Go-Ethereum](https://github.com/ethereum/go-ethereum). Keep
* Our special respect and gratitude is to the core team of [Go-Ethereum](https://github.com/ethereum/go-ethereum). Keep
up the great job!
Happy testing! 🥤
@ -596,7 +596,7 @@ Application
`htop` on column `res` shows memory of "App + OS used to hold page cache for given App", but it's not informative,
because if `htop` says that app using 90% of memory you still can run 3 more instances of app on the same machine -
because most of that `90%` is "OS pages cache".
OS automatically free this cache any time it needs memory. Smaller "page cache size" may not impact performance of
OS automatically frees this cache any time it needs memory. Smaller "page cache size" may not impact performance of
Erigon at all.
Next tools show correct memory usage of Erigon:
@ -613,8 +613,8 @@ memory.
**Warning:** Multiple instances of Erigon on same machine will touch Disk concurrently, it impacts performance - one of
main Erigon optimisations: "reduce Disk random access".
"Blocks Execution stage" still does much random reads - this is reason why it's slowest stage. We do not recommend run
multiple genesis syncs on same Disk. If genesis sync passed, then it's fine to run multiple Erigon on same Disk.
"Blocks Execution stage" still does many random reads - this is reason why it's slowest stage. We do not recommend running
multiple genesis syncs on same Disk. If genesis sync passed, then it's fine to run multiple Erigon instances on same Disk.
### Blocks Execution is slow on cloud-network-drives