posthog-performance-tuning
Optimize PostHog performance: local flag evaluation, client batching config, event sampling, efficient HogQL queries, and serverless flush patterns. Trigger: "posthog performance", "optimize posthog", "posthog latency", "posthog caching", "posthog slow", "posthog batch", "posthog fast".
What this skill does
# PostHog Performance Tuning
## Overview
Optimize PostHog for production workloads. The biggest performance wins are: local feature flag evaluation (eliminates network calls), proper batching configuration, event sampling for high-volume apps, and efficient HogQL queries with date filters.
## Prerequisites
- `posthog-node` and/or `posthog-js` installed
- Personal API key (`phx_...`) for local flag evaluation
- Feature flags configured (if applicable)
## Instructions
### Step 1: Enable Local Feature Flag Evaluation
The single biggest performance improvement. Without local evaluation, every `getFeatureFlag()` call makes a network request (~50-200ms). With local evaluation, flag definitions are cached and evaluation is instant (~0.1ms).
```typescript
import { PostHog } from 'posthog-node';
const posthog = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {
host: 'https://us.i.posthog.com',
// This is the key: personal API key enables local flag evaluation
personalApiKey: process.env.POSTHOG_PERSONAL_API_KEY,
// Flag definitions are polled every 30 seconds by default
// Adjust if you need faster flag updates:
// featureFlagsPollingInterval: 10000, // 10 seconds
});
// With personalApiKey set, this evaluates locally (no network call)
const variant = await posthog.getFeatureFlag('pricing-experiment', 'user-123', {
personProperties: { plan: 'pro', country: 'US' },
});
// Get all flags at once (still local, still fast)
const allFlags = await posthog.getAllFlags('user-123', {
personProperties: { plan: 'pro' },
groupProperties: { company: { industry: 'SaaS' } },
});
```
### Step 2: Optimize Client Batching
```typescript
// Production: batch events for network efficiency
const posthog = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {
host: 'https://us.i.posthog.com',
flushAt: 20, // Send batch when 20 events accumulated (default)
flushInterval: 10000, // Or flush every 10 seconds (default)
requestTimeout: 10000, // 10 second timeout per request
maxRetries: 3, // Retry failed sends
});
// Serverless: flush immediately (function may exit)
const serverless = new PostHog(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {
host: 'https://us.i.posthog.com',
flushAt: 1, // Send every event immediately
flushInterval: 0, // Don't wait
});
// CRITICAL: Always shutdown before process exits
process.on('SIGTERM', async () => {
await posthog.shutdown();
process.exit(0);
});
```
### Step 3: Event Sampling (Browser)
```typescript
import posthog from 'posthog-js';
posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {
api_host: 'https://us.i.posthog.com',
before_send: (event) => {
// Always capture business-critical events
const alwaysCapture = ['purchase', 'signup', 'subscription_started', 'subscription_canceled'];
if (alwaysCapture.includes(event.event)) return event;
// Sample high-volume events
const sampleRates: Record<string, number> = {
'$pageview': 1.0, // Keep all pageviews
'$pageleave': 0.5, // Sample 50%
'$autocapture': 0.1, // Sample 10% of autocapture
'scroll_depth': 0.05, // Sample 5%
};
const rate = sampleRates[event.event] ?? 0.5;
if (Math.random() >= rate) return null; // Drop event
// Tag sampled events so you can adjust in analysis
event.properties = { ...event.properties, $sample_rate: rate };
return event;
},
});
```
### Step 4: Efficient HogQL Queries
```typescript
async function queryPostHog(hogql: string) {
const response = await fetch(
`https://app.posthog.com/api/projects/${process.env.POSTHOG_PROJECT_ID}/query/`,
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
Authorization: `Bearer ${process.env.POSTHOG_PERSONAL_API_KEY}`,
},
body: JSON.stringify({
query: { kind: 'HogQLQuery', query: hogql },
}),
}
);
return response.json();
}
// FAST: Filtered by time, limited results
const fast = await queryPostHog(`
SELECT
properties.$current_url AS url,
count() AS views,
uniq(distinct_id) AS visitors
FROM events
WHERE event = '$pageview'
AND timestamp > now() - interval 7 day
GROUP BY url
ORDER BY views DESC
LIMIT 50
`);
// SLOW (avoid): No time filter, scans entire table
// SELECT * FROM events WHERE event = '$pageview'
// OPTIMIZED: Use subqueries for complex analysis
const retention = await queryPostHog(`
SELECT
dateTrunc('week', first_seen) AS cohort_week,
dateTrunc('week', timestamp) AS activity_week,
uniq(distinct_id) AS users
FROM events
INNER JOIN (
SELECT distinct_id, min(timestamp) AS first_seen
FROM events
WHERE event = 'user_signed_up'
AND timestamp > now() - interval 90 day
GROUP BY distinct_id
) AS cohorts ON events.distinct_id = cohorts.distinct_id
WHERE timestamp > now() - interval 90 day
GROUP BY cohort_week, activity_week
ORDER BY cohort_week, activity_week
`);
```
### Step 5: Session Recording Performance
```typescript
// Limit session recording to reduce data volume and cost
posthog.init(process.env.NEXT_PUBLIC_POSTHOG_KEY!, {
api_host: 'https://us.i.posthog.com',
session_recording: {
// Only record 10% of sessions
sampleRate: 0.1,
// Minimum session duration to record (skip quick bounces)
minimumDurationMilliseconds: 5000,
// Mask all text inputs by default
maskAllInputs: true,
// Mask specific CSS selectors
maskTextSelector: '.sensitive-data',
},
});
```
## Performance Benchmarks
| Operation | Without Optimization | With Optimization |
|-----------|---------------------|-------------------|
| Feature flag evaluation | 50-200ms (network) | <1ms (local eval) |
| Event capture | Individual sends | Batched (20 events/req) |
| HogQL query (7d) | 2-5s | <1s (with filters) |
| HogQL query (no filter) | 30-60s (timeout risk) | N/A (always filter) |
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Events dropped on exit | No shutdown hook | Add `posthog.shutdown()` to SIGTERM handler |
| Flag evaluation slow | No `personalApiKey` | Add personal API key for local evaluation |
| High event cost | Capturing everything | Implement `before_send` sampling |
| HogQL timeout | No date filter | Always include `timestamp > now() - interval N day` |
| Session recordings large | Recording all sessions | Set `sampleRate` to 0.1-0.25 |
## Output
- Local feature flag evaluation (<1ms per check)
- Optimized batching configuration
- Event sampling with `before_send`
- Efficient HogQL query patterns
- Session recording sampling
## Resources
- [PostHog Local Evaluation](https://posthog.com/docs/feature-flags/local-evaluation)
- [PostHog Node SDK Config](https://posthog.com/docs/libraries/node)
- [HogQL Documentation](https://posthog.com/docs/sql)
- [Session Recording Config](https://posthog.com/docs/session-replay/how-to-control-which-sessions-you-record)
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.