algolia-performance-tuning

# Algolia Performance Tuning ## Overview Algolia's edge infrastructure typically delivers search in < 50ms globally. When performance degrades, the causes are usually: oversized records, too many searchable attributes, unoptimized faceting, or missing client-side caching. This skill covers server-side and client-side optimizations. ## Performance Baselines | Metric | Good | Warning | Action Needed | |--------|------|---------|---------------| | Search latency (P50) | < 20ms | 20-100ms | > 100ms | | Search latency (P95) | < 50ms | 50-200ms | > 200ms | | Indexing time per 1K records | < 2s | 2-10s | > 10s | | Record size (avg) | < 5KB | 5-50KB | > 50KB | ## Instructions ### Step 1: Optimize Record Size ```typescript import { algoliasearch } from 'algoliasearch'; const client = algoliasearch(process.env.ALGOLIA_APP_ID!, process.env.ALGOLIA_ADMIN_KEY!); // BAD: Full record with unnecessary data const badRecord = { objectID: '1', name: 'Running Shoes', full_html_description: '<div>...5000 chars of HTML...</div>', // Too big internal_notes: 'Supplier ref: ABC-123', // Not searchable all_reviews: [/* 200 reviews */], // Huge array }; // GOOD: Lean record for search const goodRecord = { objectID: '1', name: 'Running Shoes', description: 'Lightweight running shoes with cushioned sole', // Plain text, truncated category: 'shoes', brand: 'Nike', price: 129.99, rating: 4.5, review_count: 200, ...