9 posts tagged with "db-sync"

High level summary​

Lower level summary​

• Prepared a schema change which is expected to speed up queries and help clients #1389.
• Ran a big number of benchmarks on the above to evaluate if this change is reasonable.
• Performance optimization related to rewards #1382
• Using the cache in more places to reduce recourses usage #1380
• Evaluated risks related to UTXO-HD integration
• Worked on a feauture request to split the tx_out to an address table #1396
• Worked on another feauture request to prune the consumed entries from the tx_out table #1398
• Prepared for CIP-1694 integration

High level summary​

The DBSync team worked in performance enhancements issues, on providing new db-sync options and on technical debt and bug fixing. The DBSync team also on boarded a new member.

Low level summary​

• Worked on an issue which causes ada_pots tables to include the values related not only to an epoch, but also the first epoch of the last epoch. #1367
• Fixed an issue where the epoch table didn't rollback and caused wrong values #1370
• Fixed an issue were users with disable-ledger option had to provide the state dir option, even though it was never used. Also refactored the no ledger part of the codebase. #1378
• Improved the perforance by using the cache more. Also provided many new options which enables or disables parts of db-sync. In addition a new --turbo mode is enables which allows db-sync to sync mainnet in hours. #1379

High level summary​

The db-sync team created a new tag 13.1.0.2 which is ready to release. We also investigated and had the first working UTxO-HD integration which is one of the potential future risks for db-sync.

Low level summary​

• Integrated the UTxO-HD feauture branch in kderme/utxo-hd-1. This doesn't use the full on disk storage but keeps things in memory and the plan is to keep it this way for the first iteration. The integration still has some performance issues which we investigate
• Created tag 13.1.0.2 which upgrades the dependencies of db-sync
• Fixed an issue related to errors appearing in SMASH #1353
• Continued with ghc-9.2 integration #1339
• Worked on an new fixing procedure for #1348. We try to make these procedures work also on older schema version, without the need to migrate to newer schema, which can be very useful for fixing existing snapshots.

High level summary​

After spending the last months on improving DBSync and releasing 13.1.0.0 the DBSync team focused the last weeks on integrating upstream changes and tech debt. This includes integrating CHaP, the new leger core and ghc-9.2.4

Lower level summary​

• Integrate CHaP #1331
• Integrate new ledger core 0.1.1.1 and ghc-9.2 #1332
• Technical debt: Add code formatter fourmolu #1334
• Preparing and tracking Conway and UTxO integration

High level summary​

The DBSync team continued testing release 13.1.0.0. The QA team has reported that no issues have been found. The DBSync team also worked on cherry-picks back to master and on fixing bugs.

Lower level summary​

• Release is cherry-picked back to master, which uses the new rollback mechanism which uses reverse indexes, same as the release #1320 This also fixes a bug number of issues on master.
• Depenencies upgrade and CHaP integration #1324
• AdaPots fix #1323. This fixes an issue where the per epoch AdaPots didn't match the epoch boundary, but they also included changes from the first block of the epoch.
• Deposits Event fix #3212. This pr adjusts the Deposits ledger events, so that it can be better used by db-sync. This can reduce the number of queries that db-sync does during syncing an make syncing faster.