Results for “cluster-sizing”

Clustering Based Design Skill

Risk managers should SIZE trades, not BLOCK them. Trigger when: (1) capital manager blocks trades, (2) risk manager rejects orders, (3) trades fail due to 'exceeds limit', (4) components don't work in harmony.

Optimizes Qdrant query performance for large limits across multiple shards by using Poisson-distributed subsampling to reduce inter-shard data transfer.

Guides vertical scaling decisions for Qdrant vector databases, covering when to scale up, how to resize nodes in Qdrant Cloud or self-hosted deployments, RAM sizing formulas, and when to switch to horizontal scaling.

Guides scaling Qdrant query throughput (QPS) through performance tuning, horizontal scaling with read replicas, and disk I/O optimization.

Clusters a GitHub issue backlog by root cause into plan-master issues, redirects children with a standardized comment, and bundles architectural-fix PRs that close clusters atomically.

Calculate risk-based position sizes for long stock trades using fixed fractional, ATR-based, or Kelly Criterion methods with portfolio constraints.

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues.

Extends effective context capacity through strategic compression, masking, caching, and partitioning techniques.

Expert guidance for distributed NoSQL databases (Cassandra, DynamoDB). Focuses on mental models, query-first modeling, single-table design, and avoiding hot partitions in high-scale systems.

CapsFusion: Rethinking Image-Text Data at Scale

Detect which HPC cluster you are on and load the correct job submission instructions. Use when the user asks to submit, run, or schedule a job, or when you need to know which cluster environment you are in.

Apache Spark, Hadoop, distributed computing, and large-scale data processing for petabyte-scale workloads

Copy-Paste Augmentation for Instance Segmentation

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

Data-Centric Artificial Intelligence: A Survey

Use to design or fix a customer support survey — CSAT, NPS, or CES — and to diagnose response bias. Trigger for "design a CSAT survey", "our CSAT doesn't match reality", "should we use NPS", survey response rate, non-response bias, survey timing or scale choice, comparing satisfaction across teams or channels, or interpreting a satisfaction trend.