Results for “throttling”

Every autoscaling decision is driven by one of three trigger types, and mature

Diagnoses and resolves slow Qdrant indexing and data ingestion by optimizing batching, sharding, HNSW parameters, and payload indexing strategies.

Guides optimization of Qdrant query latency by tuning segments, memory, quantization, and search parameters.

Diagnoses Qdrant production issues using metrics and observability tools, covering optimizer problems, memory spikes, and slow queries.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Diagnose frame-rate bottlenecks (CPU vs GPU bound FIRST), control Unreal Insights traces, sample live frame times, and annotate performance captures. Use when FPS is low/bad, the game is slow, or you need to find what is limiting the frame rate.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Move issues and external pull requests through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Trigger: tech stack, preferred tools, SvelteKit, Bun, Drizzle, Zero Sync, Better Auth, Vite. Scope: Project tooling preferences, framework selections. Boundary: Excludes application logic or visual styling guidelines.

Use when content is verbose, repetitive, or padded and needs tightening while preserving meaning

Eng manager-mode plan review. (gstack)

Use when investigating a bug, runtime error, unexpected behavior, test failure, or crash. For systematic root cause analysis, error message interpretation, stack trace reading, reproduction steps, and targeted fixes. Activate when the user says "it's broken", "this doesn't work", "I'm getting an error", or "help me debug".

Diagnose and remove FPS caps so the editor and game run uncapped (or at a target FPS). Use when the user says the editor/game is "locked", "capped", or "stuck" at a frame rate (commonly 60 FPS), asks to "unlock"/"uncap"/"raise" FPS, or wants to set a max FPS. Covers t.MaxFPS, VSync, fixed/smoothed frame rate, and background CPU throttling (EngineSettingsService).

Use for writing, reviewing, debugging, or testing bounded retry policies in Python with Tenacity, including retry predicates, stop and wait strategies, jitter, exception propagation, callbacks, Retrying, and AsyncRetrying. Do not use for generic loops, scheduled jobs, domain polling without a retryable operation, or operations whose side effects are not safe to repeat.

当个人或团队因拖延、分心或动力不足，导致重要目标长期停滞不前，需要一种强制机制来激发高度专注和行动力时

GRIZZLY v3.0 — BTC Alpha Hunter. Tightened configs. 7x leverage. 360-minute timeout. No thesis exit. Plugin runtime DSL.

Freeze

Use for identifying and resolving performance bottlenecks.

Freeze

The annual compliance scramble exists because controls are tested once, by

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Synthesize retrospectives into themes, root causes, decisions, and team improvements.

Diagnose and eliminate performance bottlenecks across web, API, database, and code with load testing, profiling, and optimization techniques.