customerio-performance-tuning

# Customer.io Performance Tuning ## Overview Optimize Customer.io API performance for high-volume integrations: HTTP connection pooling, identify deduplication caching, event batching with flush control, fire-and-forget async tracking, and regional routing. ## Prerequisites - Working Customer.io integration - Understanding of your traffic patterns and volume - Monitoring to measure improvement (see `customerio-observability`) ## Performance Targets | Operation | Baseline | Optimized | Technique | |-----------|----------|-----------|-----------| | Single identify | ~200ms | ~80ms | Connection pooling | | Single track | ~200ms | ~80ms | Connection pooling | | 100 events batch | ~20s serial | ~500ms | Parallel batching | | Duplicate identify | ~200ms | ~0ms | Dedup cache | | Non-critical track | Blocking | Non-blocking | Fire-and-forget | ## Instructions ### Step 1: HTTP Connection Pooling ```typescript // lib/customerio-pooled.ts import { TrackClient, RegionUS } from "customerio-node"; import https from "https"; // The customerio-node SDK creates new connections by default. // Reuse connections with a keep-alive agent. const agent = new https.Agent({ keepAlive: true, maxSockets: 25, // Max concurrent connections maxFreeSockets: 10, // Keep idle connections open timeout: 30000, // 30s socket timeout keepAliveMsecs: 15000, // TCP keep-alive probe interval }); // Apply to the SDK by creating a singleton with the agent // Note: customerio-node ...