perf(db): add rollup indexes #558
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for @blobscan/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
283.64 KB (🟡 +38.02 KB) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
New Pages Added
The following pages were added to the bundle from the code in this PR:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/block_neighbor |
251 B |
283.88 KB | 81.11% |
/stats |
347.49 KB |
631.13 KB | 180.32% |
Eight Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load | % of Budget (350 KB) |
|---|---|---|---|
/ |
352.28 KB |
635.92 KB | 181.69% (🟢 -4.87%) |
/address/[address] |
27.29 KB |
310.93 KB | 88.84% (🟢 -4.70%) |
/blob/[hash] |
27.34 KB |
310.98 KB | 88.85% (🟢 -4.31%) |
/blobs |
75.95 KB |
359.59 KB | 102.74% (🟡 +12.32%) |
/block/[id] |
14.13 KB |
297.77 KB | 85.08% (🟢 -4.21%) |
/blocks |
73.67 KB |
357.31 KB | 102.09% (🟡 +12.31%) |
/tx/[hash] |
15.53 KB |
299.17 KB | 85.48% (🟡 +0.65%) |
/txs |
73.15 KB |
356.78 KB | 101.94% (🟡 +10.30%) |
Details
Only the gzipped size is provided here based on an expert tip.
First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #558 +/- ##
=======================================
Coverage 89.37% 89.37%
=======================================
Files 150 150
Lines 9913 9913
Branches 1035 1035
=======================================
Hits 8860 8860
Misses 1053 1053 ☔ View full report in Codecov by Sentry. |
|
The issue is still present. |
Checklist
Description
Resolves #547
This PR introduces the following indexes to the
Transactionmodel:(category, rollup, block_number, index): This index allows efficient filtering by category and rollup, while ensuring the results are sorted byblock_numberandindexwithout needing an additional sorting step.(fromId, block_number, index): Similar to the above, this index enables filtering by the transaction sender (fromId), while also returning results sorted byblock_numberandindex.(toId, block_number, index): Like the previous index, but this one allows filtering by the transaction receiver (toId), with results also sorted byblock_numberandindex.Motivation and Context (Optional)
Some filtering queries on the client have been experiencing timeouts, particularly when filtering blobs by rollup. This occurs because PostgreSQL needs to perform a full table scan to locate rows that match the selected rollup values.
Related Issue (Optional)
Screenshots (if appropriate):