Skip to content

chore: lower 10k -> 2k transactions in dedicated Engine transactions chart #7659

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

arcoraven
Copy link
Contributor

@arcoraven arcoraven commented Jul 21, 2025

[Dashboard] Fix: Reduce transaction query limit to improve performance

Notes for the reviewer

Reduced the transaction query limit from 10,000 to 2,000 in the TransactionCharts component to improve performance and reduce potential load on the backend.

How to test

Verify that the transactions table still loads properly with the reduced limit and that performance is improved, especially for instances with many transactions.

Summary by CodeRabbit

  • Refactor
    • Reduced the maximum number of transactions fetched for charts from 10,000 to 2,000, optimizing data handling in the transactions overview.

Copy link

changeset-bot bot commented Jul 21, 2025

⚠️ No Changeset found

Latest commit: 1309cd0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

vercel bot commented Jul 21, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
thirdweb-www 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jul 21, 2025 3:22pm
4 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Skipped (Inspect) Jul 21, 2025 3:22pm
nebula ⬜️ Skipped (Inspect) Jul 21, 2025 3:22pm
thirdweb_playground ⬜️ Skipped (Inspect) Jul 21, 2025 3:22pm
wallet-ui ⬜️ Skipped (Inspect) Jul 21, 2025 3:22pm

Copy link
Contributor

coderabbitai bot commented Jul 21, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The change updates the TransactionCharts component to reduce the limit parameter for fetching transactions from 10,000 to 2,000. No other logic, control flow, or error handling is modified, and there are no changes to exported or public entity declarations.

Changes

File Path Change Summary
.../engine/dedicated/(instance)/[engineId]/overview/components/transactions-table.tsx Reduced transaction fetch limit from 10,000 to 2,000

Estimated code review effort

1 (~2 minutes)


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a534580 and 1309cd0.

📒 Files selected for processing (1)
  • apps/dashboard/src/app/(app)/team/[team_slug]/[project_slug]/(sidebar)/engine/dedicated/(instance)/[engineId]/overview/components/transactions-table.tsx (1 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@arcoraven arcoraven marked this pull request as ready for review July 21, 2025 15:22
@arcoraven arcoraven requested review from a team as code owners July 21, 2025 15:22
@github-actions github-actions bot added the Dashboard Involves changes to the Dashboard. label Jul 21, 2025
Copy link
Contributor Author

arcoraven commented Jul 21, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • merge-queue - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@arcoraven arcoraven added the merge-queue Adds the pull request to Graphite's merge queue. label Jul 21, 2025
@arcoraven arcoraven merged commit 01daace into main Jul 21, 2025
21 of 23 checks passed
@arcoraven arcoraven deleted the ph/07-21-chore_lower_engine_v2_transactions_chart_to_2k_transactions branch July 21, 2025 15:23
Copy link
Contributor Author

Merge activity

  • Jul 21, 3:23 PM UTC: The merge label 'merge-queue' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

Copy link

codecov bot commented Jul 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.40%. Comparing base (a534580) to head (1309cd0).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7659   +/-   ##
=======================================
  Coverage   56.40%   56.40%           
=======================================
  Files         908      908           
  Lines       58228    58228           
  Branches     4226     4226           
=======================================
  Hits        32844    32844           
  Misses      25274    25274           
  Partials      110      110           
Flag Coverage Δ
packages 56.40% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
thirdweb (esm) 63.23 KB (0%) 1.3 s (0%) 221 ms (+170.92% 🔺) 1.5 s
thirdweb (cjs) 353.45 KB (0%) 7.1 s (0%) 700 ms (+9.72% 🔺) 7.8 s
thirdweb (minimal + tree-shaking) 5.7 KB (0%) 114 ms (0%) 96 ms (+1383.79% 🔺) 210 ms
thirdweb/chains (tree-shaking) 526 B (0%) 11 ms (0%) 37 ms (+2303.94% 🔺) 47 ms
thirdweb/react (minimal + tree-shaking) 19.59 KB (0%) 392 ms (0%) 97 ms (+856.83% 🔺) 489 ms

@arcoraven arcoraven changed the title only one file chore: lower 10k -> 2k transactions in dedicated Engine transactions chart Jul 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dashboard Involves changes to the Dashboard. merge-queue Adds the pull request to Graphite's merge queue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant