Skip to content

Conversation

@nikochiko
Copy link
Member

Legal Boilerplate

Look, I get it. The entity doing business as “Gooey.AI” and/or “Dara.network” was incorporated in the State of Delaware in 2020 as Dara Network Inc. and is gonna need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Dara Network Inc can use, modify, copy, and redistribute my contributions, under its choice of terms.

@coderabbitai
Copy link

coderabbitai bot commented Jun 27, 2025

Walkthrough

This change updates deployment documentation and configuration files to reflect adjustments in replica counts and autoscaling settings for several services. In the documentation, replica counts for multiple deployments were reduced, with some set to zero, and new model IDs were added to certain deployments. In the YAML configuration, the minimum replica count (minReplicaCount) for several deployments was explicitly set to zero or reduced, allowing those services to scale down to fewer or no active replicas. No changes were made to public code entities, and the overall structure of the files remains unchanged.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
chart/model-values.yaml (3)

57-61: Scale-to-zero for heavyweight diffusion models – check cold-start SLA

minReplicaCount has been dropped to 0 for five diffusion deployments.
Cold-starting a 35–50 Gi GPU image that has to pull >10 GB of model weights can add several minutes of latency, especially when an idle node has to be re-provisioned.

• Verify that KEDA’s queue-length trigger plus your client time-outs can tolerate this extra spin-up time.
• If not, keep one warm replica or add a pre-warm job/lifecycle hook.

Also applies to: 73-75, 88-90, 101-104, 118-121


130-136: deforum-sd-1 now scales to zero – very long start-up expected

deforum-sd-1 loads Deforum + Stable Diffusion + animation tool-chain. Historical data shows first-frame latency >6 min from cold. Confirm that the product flow (e.g., webhook ACK time) is bumped accordingly or that a warming strategy is in place.


171-187: Many speech & embedding services also moved to minReplicaCount = 0

While these models are lighter than SD, Whisper‐large and Embedding transformers still take 60-90 s to load on A100s. Make sure:

  1. The HPA/KEDA cooldown period is long enough to prevent thrashing.
  2. Any “sync” or “streaming” endpoints that expect <5 s cold latency are routed to the few services that still keep one replica.

Also applies to: 198-215, 224-229, 238-242, 265-270, 277-282, 299-305

DEPLOYMENTS.md (1)

27-28: Lint warning – wrap bare URLs to satisfy MD034

markdownlint flagged bare URLs in the table. Wrap them, e.g.:

<https://objectstore.e2enetworks.net/indic-asr-public/checkpoints/...>
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4a6a8d7 and 1fc0d18.

📒 Files selected for processing (2)
  • DEPLOYMENTS.md (1 hunks)
  • chart/model-values.yaml (6 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
DEPLOYMENTS.md

27-27: Bare URL used
null

(MD034, no-bare-urls)


28-28: Bare URL used
null

(MD034, no-bare-urls)

🔇 Additional comments (2)
chart/model-values.yaml (1)

317-322: retro-sadtalker & retro-wav2lip keep 1 warm replica – good compromise

Retaining a single replica for these real-time lip-sync services protects UX while still allowing scale-out. 👍

Also applies to: 332-336

DEPLOYMENTS.md (1)

8-18: Docs accurately reflect new replica counts

The table mirrors the YAML changes (many replicas → 0). Looks in-sync.

@nikochiko nikochiko merged commit e04d993 into main Jul 10, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants