lokalise-performance-tuning

# Lokalise Performance Tuning ## Overview Optimize Lokalise API throughput for translation pipelines by implementing cursor pagination, local caching, batch key operations (500/request), request throttling under the 6 req/s rate limit, and selective language downloads. ## Prerequisites - `@lokalise/node-api` SDK v9+ (ESM) or REST API access - `LOKALISE_API_TOKEN` environment variable set - Understanding of project size (key count, language count) to calibrate batch sizes - Optional: Redis or LRU cache library for persistent caching ## Instructions ### Step 1: Use Cursor Pagination for Large Datasets Cursor pagination is significantly faster than offset pagination for projects with 5K+ keys. Offset pagination degrades as page numbers increase because the server must skip rows; cursor pagination uses a pointer. ```typescript import { LokaliseApi } from '@lokalise/node-api'; const lok = new LokaliseApi({ apiKey: process.env.LOKALISE_API_TOKEN! }); // Generator that yields all keys using cursor pagination async function* getAllKeys(projectId: string) { let cursor: string | undefined; do { const result = await lok.keys().list({ project_id: projectId, limit: 500, // Maximum allowed per request pagination: 'cursor', cursor, }); for (const key of result.items) yield key; cursor = result.hasNextCursor() ? result.nextCursor : undefined; } while (cursor); } // Usage: 10,000 keys = 20 API calls (vs 100 with default limi...