customerio-performance-tuning

Optimize Customer.io API performance for high throughput. Use when improving response times, implementing connection pooling, batching, caching, or regional routing. Trigger: "customer.io performance", "optimize customer.io", "customer.io latency", "customer.io connection pooling".

Aller à l'installation

Dépôt: jeremylongshore/claude-code-plugins-plus-skills
Dernière activité de la source: 17 juillet 2026 à 22:18
Langue détectée de SKILL.md: anglais
Étoiles: 2 604
Forks: 378

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill customerio-performance-tuning

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Explorateur de fichiers

3 fichiers

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

2026-07-23

clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

2026-07-23

clerk-enterprise-rbac

Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".

2026-07-23

Tout voir dans ce dépôt

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

// 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: , : , }); https. = agent; cio = ( process..!, process..!, { : } ); { cio };

name	customerio-performance-tuning
description	Optimize Customer.io API performance for high throughput. Use when improving response times, implementing connection pooling, batching, caching, or regional routing. Trigger: "customer.io performance", "optimize customer.io", "customer.io latency", "customer.io connection pooling".
allowed-tools	Read, Write, Edit, Bash(npm:), Bash(npx:), Glob, Grep
version	1.14.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","customer-io","performance","optimization"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Customer.io Performance Tuning

Overview

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

// 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: ,        
  : , 
});




https. = agent;


 cio =  (
  process..!,
  process..!,
  { :  }
);

 { cio };

// lib/customerio-batch.ts import { TrackClient, RegionUS } from "customerio-node"; interface BatchItem { type: "identify" | "track"; userId: string; data: Record<string, any>; } export class CioBatchProcessor { private buffer: BatchItem[] = []; private timer: NodeJS.Timeout | null = null; private client: TrackClient; private processing = false; constructor( private readonly maxBatchSize = 100, private readonly flushIntervalMs = 3000, private readonly concurrency = 15 ) { this.client = new TrackClient( process.env.CUSTOMERIO_SITE_ID!, process.env.CUSTOMERIO_TRACK_API_KEY!, { region: RegionUS } ); this.startFlushTimer(); } add(item: BatchItem): void { this.buffer.push(item); if (this.buffer.length >= this.maxBatchSize) { this.flush(); } } async flush(): Promise<void> { if (this.processing || this.buffer.length === 0) return; this.processing = true; const batch = this.buffer.splice(0, this.maxBatchSize); const startMs = Date.now(); // Process in parallel chunks for (let i = 0; i < batch.length; i += this.concurrency) { const chunk = batch.slice(i, i + this.concurrency); const results = await Promise.allSettled( chunk.map((item) => item.type === "identify" ? this.client.identify(item.userId, item.data) : this.client.track(item.userId, item.data) ) ); const failed = results.filter((r) => r.status === "rejected").length; if (failed > 0) { console.warn(`CIO batch: ${failed}/${chunk.length} failed`); } } const elapsed = Date.now() - startMs; console.log(`CIO batch: ${batch.length} items in ${elapsed}ms`); this.processing = false; } private startFlushTimer(): void { this.timer = setInterval(() => this.flush(), this.flushIntervalMs); } async shutdown(): Promise<void> { if (this.timer) clearInterval(this.timer); await this.flush(); } }

Issue	Solution
High p99 latency	Enable connection pooling, check DNS resolution
Timeout errors	Increase timeout, reduce payload size
Memory growth	Cap LRU cache size, limit batch buffer
Dedup cache misses	Increase TTL if same identify calls are >5min apart

customerio-performance-tuning

Options d'installation

Vérifiez les fichiers source

Customer.io Performance Tuning

Overview

Prerequisites

Performance Targets

Instructions

Step 1: HTTP Connection Pooling

Customer.io Performance Tuning

Overview

Prerequisites

Performance Targets

Instructions

Step 1: HTTP Connection Pooling

Step 2: Identify Deduplication Cache

Step 3: Batch Processor

Step 4: Fire-and-Forget Async Tracking

Step 5: Regional Routing

Performance Monitoring

Error Handling

Resources

Next Steps

customerio-performance-tuning

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

Customer.io Performance Tuning

Overview

Prerequisites

Performance Targets

Instructions

Step 1: HTTP Connection Pooling

Customer.io Performance Tuning

Overview

Prerequisites

Performance Targets

Instructions

Step 1: HTTP Connection Pooling

Step 2: Identify Deduplication Cache

Step 3: Batch Processor

Step 4: Fire-and-Forget Async Tracking

Step 5: Regional Routing

Performance Monitoring

Error Handling

Resources

Next Steps