69b0ccb4b8
Cross-referenced all 70+ KB files against official Oracle docs. Critical fixes: - ExaCS: storage was flash cache not usable disk (76.8→190.8 TB QR), added X11M, removed X10M - ADB-S: OCPU→ECPU migration, 26ai as default, cross-region RTO 15→10 min - Compute: E5 max 94→126, A2 80→78, added E6/A4/BM shapes, 11 GPU shapes - Storage: Higher Perf IOPS 35K→50K, UHP 450K→300K, File Storage 25K→50K - DBCS: E5.Flex max 94→64, storage 80→150 TB, added 26ai - Networking: FastConnect +400 Gbps, NSG max 120 rules Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
59 lines
2.2 KiB
YAML
59 lines
2.2 KiB
YAML
---
|
|
last_verified: 2026-03-14
|
|
description: ADB-S auto-scaling behavior, timing, and sizing implications.
|
|
---
|
|
|
|
auto_scaling:
|
|
notes: "OCPU is legacy billing. ECPU is now default. 1 OCPU ≈ 4 ECPUs."
|
|
ocpu_scaling:
|
|
trigger: "CPU demand exceeds current allocation"
|
|
max_scale: "3x base OCPUs/ECPUs (up to 128 OCPU / 512 ECPU maximum)"
|
|
ramp_up_time: "2-3 minutes to begin scaling"
|
|
ramp_down_time: "After sustained low utilization (5-10 minutes)"
|
|
billing: "Only billed during active scaling period, per OCPU per second"
|
|
|
|
storage_scaling:
|
|
trigger: "Storage usage approaches allocated storage"
|
|
behavior: "Auto-expands storage allocation"
|
|
billing: "Billed for allocated storage"
|
|
|
|
sizing_recommendations:
|
|
base_ocpu_strategy: |
|
|
Size base OCPUs for P75 utilization, not average.
|
|
Auto-scaling handles P95+ bursts, but the 2-3 minute ramp-up
|
|
means very short spikes may complete before scaling activates.
|
|
|
|
guidelines:
|
|
- scenario: "Steady OLTP workload"
|
|
base: "P75 utilization"
|
|
auto_scale: "Enable, set max to P95 or 2x base"
|
|
- scenario: "Highly variable workload (2x+ peak/baseline)"
|
|
base: "P50 utilization"
|
|
auto_scale: "Enable, set max to 3x base"
|
|
- scenario: "Batch processing with known peak times"
|
|
base: "Baseline requirement"
|
|
auto_scale: "Enable, supplement with scheduled scaling if available"
|
|
- scenario: "Dev/test"
|
|
base: "1-2 OCPUs"
|
|
auto_scale: "Disable to control costs"
|
|
|
|
connection_impact:
|
|
connections_per_ocpu: 300
|
|
example: |
|
|
Base 8 OCPUs → 2,400 connections
|
|
Auto-scale to 16 OCPUs → 4,800 connections
|
|
Connection limits scale with OCPUs automatically
|
|
|
|
performance_during_scaling:
|
|
notes:
|
|
- "Active sessions are not interrupted during scale-up"
|
|
- "New connections get additional capacity immediately"
|
|
- "Scale-down uses connection draining — active sessions complete normally"
|
|
- "Brief performance dip possible during scaling transition"
|
|
|
|
gotchas:
|
|
- "Short bursts (<3 min) may complete before auto-scaling activates"
|
|
- "Very rapid burst from 0 to max can cause connection queuing"
|
|
- "Auto-scaling cost can surprise if workload is consistently above base"
|
|
- "Monitor auto-scaling events to right-size base OCPUs over time"
|