Chore: Add hardcoded-records source to profiling script

[Aaron ("AJ") Steers (aaronsteers)]

Summary by CodeRabbit

• New Features

  • Introduced a new data source option, "hardcoded," enhancing flexibility for data retrieval.
  • Updated command-line argument parsing to include the "hardcoded" source, changing the default cache type.

• Improvements

  • Modified help text for cache type to clarify the relationship between "hardcoded" and "e2e" sources.

[coderabbitai]

Walkthrough

Walkthrough

The recent updates to the script significantly enhance its functionality by introducing a new data source option labeled "hardcoded." This change allows users to access a specific source configuration while also updating command-line argument parsing to reflect this new option. The adjustments include altering the default cache type to "hardcoded," improving the script's usability and flexibility for performance testing.

Changes

Files	Change Summary
examples/run_perf_test_reads.py	Updated get_source function to handle "hardcoded" alias. Modified command-line argument parsing to include "hardcoded" as a valid choice and changed the default cache type to "hardcoded."

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant Script
    participant DataSource

    User->>CLI: Run script with --cache_type hardcoded
    CLI->>Script: Parse arguments
    Script->>DataSource: get_source("hardcoded")
    DataSource-->>Script: Return source configuration
    Script-->>CLI: Execute with hardcoded data source
    CLI-->>User: Output results

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.