Skip to content

Renderer perf experiments #323

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

Open
wants to merge 4 commits into
base: next
Choose a base branch
from
Open

Renderer perf experiments #323

wants to merge 4 commits into from

Conversation

zardoy
Copy link
Owner

@zardoy zardoy commented Apr 7, 2025

PR Type

formatting


Description

  • Minor formatting adjustment in src/optionsStorage.ts.

Changes walkthrough 📝

Relevant files
Formatting
optionsStorage.ts
Minor formatting adjustment in options storage file           

src/optionsStorage.ts

  • Adjusted whitespace in the numWorkers line.
+1/-1     

Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Bundle Size

    Summary by CodeRabbit

    • Chores
      • Updated the concurrency settings by reducing the allocated processing threads, which may influence performance and resource usage.

    Copy link

    codesandbox bot commented Apr 7, 2025

    Review or Edit in CodeSandbox

    Open the branch in Web EditorVS CodeInsiders

    Open Preview

    Copy link

    coderabbitai bot commented Apr 7, 2025

    Note

    Reviews paused

    Use the following commands to manage reviews:

    • @coderabbitai resume to resume automatic reviews.
    • @coderabbitai review to trigger a single review.

    Walkthrough

    The pull request updates the worker configuration in the options storage module. Specifically, it reduces the number of worker threads in the defaultOptions object from 4 to 2. No changes have been made to any exported or public declarations.

    Changes

    File(s) Change Summary
    src/optionsStorage.ts Modified defaultOptions: numWorkers changed from 4 to 2

    Sequence Diagram(s)

    Poem

    I’m just a rabbit, hopping through code,
    Lightening the load on my humble abode.
    With fewer workers, steady I roam,
    In this little change, I feel right at home.
    Hop along, my friends, to a simpler mode!
    🐇✨


    🪧 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.
      • Generate unit testing code for this file.
      • 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 generate unit testing code for this file.
      • @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 generate unit testing code.
      • @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.

    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 resolve resolve all the CodeRabbit review comments.
    • @coderabbitai plan to trigger planning for file edits and PR creation.
    • @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.

    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    /benchmark

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No major issues detected

    Copy link

    qodo-merge-pro-for-open-source bot commented Apr 7, 2025

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    General
    Remove trailing whitespace
    Suggestion Impact:The commit addressed the line with trailing whitespace, but instead of just removing the whitespace, it also changed the value from 4 to 2

    code diff:

    -  numWorkers: 4, 
    +  numWorkers: 2,

    Remove the trailing whitespace after the value 4. Trailing whitespaces can cause
    inconsistent formatting and potential issues with version control systems.

    src/optionsStorage.ts [81]

    [Suggestion has been applied]

    Suggestion importance[1-10]: 3

    __

    Why: The suggestion correctly identifies and addresses the trailing whitespace after "4," which is a minor code style issue. While this is a valid improvement for code cleanliness and consistency, it has minimal impact on functionality.

    Low
    • Update

    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    @coderabbitai ignore

    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    /benchmark

    @zardoy zardoy changed the title perf tests Renderer perf experiments Apr 7, 2025
    Copy link

    github-actions bot commented Apr 7, 2025

    Benchmark result: - fixture: https://bucket.mcraft.fun/Future CITY 4.4-slim.zip - -133 87 309 - 5

    • world load time seconds: 128.73
    • mesher workers count: 4.00
    • mesher process avg ms: 111.73
    • mesher process total ms: 225019.50
    • mesher process worst ms: 979.10
    • chunks full info: Q: 0 121/121/121 chunks (5:112ms/26ss/128198.0s)
    • average render time ms: 9.71
    • worst render time ms: 121.10
    • fps average prediction: 103.00
    • fps worst prediction: 8.26
    • fps average real: 4 / 60
    • fps worst real: 1.00
    • backend info report: C: 1 TR: 12 TE: 18 F: 796,071 B: 1,734,860
    • fps average main thread: 5.88
    • fps worst main thread: 2.00
    • memory usage average: 97.4 MB
    • memory usage worst: 97.4 MB
    • gpu info: ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver)
    • hardware concurrency: 4.00
    • user agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Cypress/10.11.0 Chrome/106.0.5249.51 Electron/21.0.0 Safari/537.36
    • client version: undefined 2025-04-07T13

    Copy link

    coderabbitai bot commented Apr 7, 2025

    ✅ Actions performed

    Reviews paused.

    Copy link

    github-actions bot commented Apr 7, 2025

    Benchmark result: Benchmark failed to run or produce results

    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    Repository owner deleted a comment from github-actions bot Apr 7, 2025
    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    /benchmark

    Copy link

    github-actions bot commented Apr 7, 2025

    Benchmark result: Benchmark failed to run or produce results

    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    /benchmark

    1 similar comment
    @zardoy
    Copy link
    Owner Author

    zardoy commented Apr 7, 2025

    /benchmark

    Copy link

    github-actions bot commented Apr 7, 2025

    Benchmark result: Benchmark failed to run or produce results

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    1 participant