forked from wownero/wownero
dns-fix
dev-v0.12
wow-v0.11
wow11
rebase-v0.11
dev-v0.11
testnet-v11
long-unlock
diff-v6
dev
master
fix-armv7a-compile
release-v0.10.1.0
wonerujo-v0.10.1
release-v0.10.0.3
release-v0.9.3.3
release-0.8.0.2
release-v0.7.1.0
release-v0.6.1.2
release-v0.5.1
release-v0.5.0
release-v0.4.0.1
release-v0.3.0.0
release-v0.2.2.0
release-v0.2.1.0
testnetv11
v0.10.2.1
v0.10.2.0
v0.10.1.0
v0.10.0.3
v0.10.0.2
v0.10.0.1
v10
v0.9.0.2
v0.9.0.1
v0.2.2.0
Busty-Brazzers
v0.2.0.0
alpha
wowhero
v11-dev-test
v0.9.3.3
v0.9.3.2
v0.9.3.1
v0.9.3.0
v0.9.2.2
v0.9.2.1
v0.9.2.0
v0.9.1.0
v0.9.0.0
v0.8.0.2
v0.8.0.1
v0.8.0.0
v0.7.0
v0.6.1.2
v0.6.1.1
v0.6.1.0
v0.6.0.0
v0.5.1.0
v0.5.0.2
v0.5.0.0
v0.4.0.0
v0.3.1.4
v0.3.1.3
v0.3.1.2
v0.3.1.1
v0.3.1.0
v0.3.0.0
v0.2.2.00
v0.2.1.0
v0.10.0.0
v0.1.0.0
testnet-v0.11
10.0.0
${ noResults }
4 Commits (e66866c1fc06fd8a546c2c7869f899844078e44a)
| Author | SHA1 | Message | Date |
|---|---|---|---|
kenshi84
|
8027ce0c75 |
extract some basic code from libcryptonote_core into libcryptonote_basic
|
7 years ago |
warptangent
|
725acc7f17
|
Replace tabs with two spaces for consistency with rest of codebase
Remove trailing whitespace in same files. |
9 years ago |
moneromooo-monero
|
b13e7f284b
|
blockchain_export can now export to a blocks.dat format
Also make the number of blocks endian independant, and add support for testnet |
9 years ago |
NoodleDoodleNoodleDoodleNoodleDoodleNoo
|
e5d2680094 |
** CHANGES ARE EXPERIMENTAL (FOR TESTING ONLY)
Bockchain:
1. Optim: Multi-thread long-hash computation when encountering groups of blocks.
2. Optim: Cache verified txs and return result from cache instead of re-checking whenever possible.
3. Optim: Preload output-keys when encoutering groups of blocks. Sort by amount and global-index before bulk querying database and multi-thread when possible.
4. Optim: Disable double spend check on block verification, double spend is already detected when trying to add blocks.
5. Optim: Multi-thread signature computation whenever possible.
6. Patch: Disable locking (recursive mutex) on called functions from check_tx_inputs which causes slowdowns (only seems to happen on ubuntu/VMs??? Reason: TBD)
7. Optim: Removed looped full-tx hash computation when retrieving transactions from pool (???).
8. Optim: Cache difficulty/timestamps (735 blocks) for next-difficulty calculations so that only 2 db reads per new block is needed when a new block arrives (instead of 1470 reads).
Berkeley-DB:
1. Fix: 32-bit data errors causing wrong output global indices and failure to send blocks to peers (etc).
2. Fix: Unable to pop blocks on reorganize due to transaction errors.
3. Patch: Large number of transaction aborts when running multi-threaded bulk queries.
4. Patch: Insufficient locks error when running full sync.
5. Patch: Incorrect db stats when returning from an immediate exit from "pop block" operation.
6. Optim: Add bulk queries to get output global indices.
7. Optim: Modified output_keys table to store public_key+unlock_time+height for single transaction lookup (vs 3)
8. Optim: Used output_keys table retrieve public_keys instead of going through output_amounts->output_txs+output_indices->txs->output:public_key
9. Optim: Added thread-safe buffers used when multi-threading bulk queries.
10. Optim: Added support for nosync/write_nosync options for improved performance (*see --db-sync-mode option for details)
11. Mod: Added checkpoint thread and auto-remove-logs option.
12. *Now usable on 32-bit systems like RPI2.
LMDB:
1. Optim: Added custom comparison for 256-bit key tables (minor speed-up, TBD: get actual effect)
2. Optim: Modified output_keys table to store public_key+unlock_time+height for single transaction lookup (vs 3)
3. Optim: Used output_keys table retrieve public_keys instead of going through output_amounts->output_txs+output_indices->txs->output:public_key
4. Optim: Added support for sync/writemap options for improved performance (*see --db-sync-mode option for details)
5. Mod: Auto resize to +1GB instead of multiplier x1.5
ETC:
1. Minor optimizations for slow-hash for ARM (RPI2). Incomplete.
2. Fix: 32-bit saturation bug when computing next difficulty on large blocks.
[PENDING ISSUES]
1. Berkely db has a very slow "pop-block" operation. This is very noticeable on the RPI2 as it sometimes takes > 10 MINUTES to pop a block during reorganization.
This does not happen very often however, most reorgs seem to take a few seconds but it possibly depends on the number of outputs present. TBD.
2. Berkeley db, possible bug "unable to allocate memory". TBD.
[NEW OPTIONS] (*Currently all enabled for testing purposes)
1. --fast-block-sync arg=[0:1] (default: 1)
a. 0 = Compute long hash per block (may take a while depending on CPU)
b. 1 = Skip long-hash and verify blocks based on embedded known good block hashes (faster, minimal CPU dependence)
2. --db-sync-mode arg=[[safe|fast|fastest]:[sync|async]:[nblocks_per_sync]] (default: fastest:async:1000)
a. safe = fdatasync/fsync (or equivalent) per stored block. Very slow, but safest option to protect against power-out/crash conditions.
b. fast/fastest = Enables asynchronous fdatasync/fsync (or equivalent). Useful for battery operated devices or STABLE systems with UPS and/or systems with battery backed write cache/solid state cache.
Fast - Write meta-data but defer data flush.
Fastest - Defer meta-data and data flush.
Sync - Flush data after nblocks_per_sync and wait.
Async - Flush data after nblocks_per_sync but do not wait for the operation to finish.
3. --prep-blocks-threads arg=[n] (default: 4 or system max threads, whichever is lower)
Max number of threads to use when computing long-hash in groups.
4. --show-time-stats arg=[0:1] (default: 1)
Show benchmark related time stats.
5. --db-auto-remove-logs arg=[0:1] (default: 1)
For berkeley-db only. Auto remove logs if enabled.
**Note: lmdb and berkeley-db have changes to the tables and are not compatible with official git head version.
At the moment, you need a full resync to use this optimized version.
[PERFORMANCE COMPARISON]
**Some figures are approximations only.
Using a baseline machine of an i7-2600K+SSD+(with full pow computation):
1. The optimized lmdb/blockhain core can process blocks up to 585K for ~1.25 hours + download time, so it usually takes 2.5 hours to sync the full chain.
2. The current head with memory can process blocks up to 585K for ~4.2 hours + download time, so it usually takes 5.5 hours to sync the full chain.
3. The current head with lmdb can process blocks up to 585K for ~32 hours + download time and usually takes 36 hours to sync the full chain.
Averate procesing times (with full pow computation):
lmdb-optimized:
1. tx_ave = 2.5 ms / tx
2. block_ave = 5.87 ms / block
memory-official-repo:
1. tx_ave = 8.85 ms / tx
2. block_ave = 19.68 ms / block
lmdb-official-repo (
|
9 years ago |