render-scaling

Configures autoscaling, instance counts, and plan types for Render services.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/DingJun1028/esggo-kv --skill render-scaling-dingjun1028
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: render-scaling
Source: https://github.com/DingJun1028/esggo-kv/tree/main/.agents/skills/render-scaling
Command: npx skills add https://github.com/DingJun1028/esggo-kv --skill render-scaling-dingjun1028

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Scaling Render services correctly requires knowing platform rules like the 100-instance cap, Professional-tier autoscaling requirements, disk-attached single-instance limits, and how autoscaling overrides manual counts. This Skill consolidates those rules so you configure scaling without misconfigurations or surprise costs. ## Core Features & Use Cases - Manual and Autoscaling Configuration: Set instance counts from 1 to 100 via Dashboard, CLI, API, or Blueprint, and configure CPU/memory autoscaling targets with min/max bounds. - Instance Type Selection: Choose between vertical scaling (plan upgrades from free to pro_ultra) and horizontal scaling based on workload characteristics. - Cost and Constraint Guidance: Apply per-second billing implications, spike-protected scale-down behavior, and constraints for disks, static sites, cron jobs, and preview environments. - Use Case: A web service hitting high CPU during traffic peaks needs autoscaling. Use this Skill to write a Blueprint with minInstances 2, maxInstances 10, and 70% CPU target, while avoiding the mistake of combining it with a persistent disk. ## Quick Start Ask the assistant to configure autoscaling for your Render web service with a minimum of 2 instances, a maximum of 10, and a 70 percent CPU target.

Frequently Asked Questions about render-scaling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up autoscaling on Render?▼

Autoscaling on Render requires a Professional or higher workspace. Configure it in the Dashboard under Scaling, or add a scaling block in your Blueprint with minInstances, maxInstances, and targetCPUPercent or targetMemoryPercent values between 1 and 90.

How does Render autoscaling calculate instance count?▼

Render computes new instances as ceil(current_instances times current_utilization divided by target_utilization). When both CPU and memory targets are set, it uses the larger of the two results, favoring more aggressive scale-out.

Can I scale a Render service with a persistent disk?▼

No, services with persistent disks cannot scale to multiple instances and must remain single-instance. Static sites are also not scalable since they are served by CDN, and cron jobs use a different execution model.

Why is my Render service not scaling down immediately?▼

Render intentionally delays scale-down for a few minutes after conditions allow it, as spike protection against brief load fluctuations. Scale-up happens immediately, but scale-down waits to reduce flapping.

Does numInstances override autoscaling in Render Blueprints?▼

No, autoscaling takes precedence when both a scaling block and numInstances are present in a Blueprint. The manual instance count does not override the active autoscaling policy.

What is the maximum number of instances on Render?▼

Render enforces a hard cap of 100 instances per service regardless of your autoscaling max setting. Set a practical maxInstances value as a cost ceiling to avoid excessive scaling during traffic spikes or attacks.