chore: prepare 1.4.0 #604
Open
chore: prepare 1.4.0 #604
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- 10 minute interval for pruning is too aggressive and it causes very
high I/O when syncing. Increasing it to 1 hour.
Rationale -
- Constant insert/delete cycles on address_utxo table
- Index Maintenance: Heavy I/O from index rebuilds after 264M deletions
- Write-Heavy Workload: 15:1 write-to-read ratio overwhelming storage
- configure option for pruning batch size. Default is 3000 but if needed
can be changed upto 10000 for faster deletion but it should not cause
too much I/O while syncing
- debug option for utxo store
Added new server health monitoring dashboard for CPU usage, memory usage, disk usage and other metrics for server health monitoring
matiwinnetou
force-pushed
the
develop
branch
3 times, most recently
from
a0222ab to
cfdb33f
Compare
matiwinnetou
force-pushed
the
develop
branch
from
cfdb33f to
2ce3ffc
Compare
matiwinnetou
force-pushed
the
develop
branch
from
7dc0015 to
cae0196
Compare
…ect and api.yml, currency response metadata will no longer have decimals. (#613) * refactor: token registry service now returns a specialised domain object and api.yml, currency response metadata will no longer have decimals. * feat: added logging / debug for subjects data. * fix: no longer using assetName --------- Co-authored-by: Mateusz Czeladka <mateusz.czeladka@cardanofoundation.org>
docs: Created docs for enabling token metadata and running local token registry.
❌ Preprod Tests: FAILEDTests run against preprod network with live blockchain data |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.