Performance Impact
Laritor is designed to deliver deep observability without sacrificing application performance.
While any monitoring tool introduces some degree of overhead (as it must intercept and send real-time data), Laritor is engineered to keep that impact virtually unnoticeable — even under heavy load. Here’s how:
1. 🚀 Deferred Event Transmission
Section titled “1. 🚀 Deferred Event Transmission”- Post-response dispatch: Laritor defers event transmission until after your application has responded to the user. This means event delivery never delays your response lifecycle.
- Non-blocking behavior: Data is sent in the background using Laravel’s shutdown hooks or queueable methods, depending on context.
Why it matters: Your users never wait for Laritor. Requests complete at full speed, regardless of monitoring.
2. 🌍 Edge-Location Ingestion
Section titled “2. 🌍 Edge-Location Ingestion”- Cloudflare Workers at 330+ locations: All ingestion occurs at the edge — not a centralized data center.
- Geographic proximity: Events are pushed to the closest Cloudflare region, minimizing round-trip latency.
Example: A server in Frankfurt sends data to a nearby German edge, not across the Atlantic.
3. ⚡ Sub-10 Millisecond Response Times
Section titled “3. ⚡ Sub-10 Millisecond Response Times”- Immediate acknowledgment: Our Cloudflare Workers respond with
HTTP 200 OKas soon as they receive a payload. - Async queue processing: Actual ingestion (like queuing and transformation) happens after the response — asynchronously.
- Consistent performance: This two-step approach yields single-digit millisecond responses at the edge, regardless of your application’s traffic volume.
Result: Laritor’s ingest responses consistently complete in single-digit milliseconds, even during high traffic.
4. 🧠 Minimal Processing Overhead
Section titled “4. 🧠 Minimal Processing Overhead”- No heavy abstractions: Internally, we avoid Laravel Collections, macros, and costly helpers in the critical path.
- Low-level PHP: We use native control structures and stream-based logic for faster processing and reduced CPU usage.
In performance-critical paths, we prioritize speed over syntactic sugar.
5. 📦 Lightweight Package
Section titled “5. 📦 Lightweight Package”- Tiny install size: The full Composer package is under ~100 KB when compressed.
- Minimal files: The client includes fewer than 50 files — no unnecessary bloat or third-party overhead.
Easy to install. Easy to maintain. Zero friction.
⚠️ What About High-Traffic Applications?
Section titled “⚠️ What About High-Traffic Applications?”For very high throughput systems, where requests arrive faster than PHP workers can recycle:
- Deferred transmission is still used, but the background HTTP call can temporarily hold the worker process open.
- To address this, edge ingestion and non-blocking ACKs dramatically reduce hold time — often under 10ms.
✅ Summary
Section titled “✅ Summary”| Optimization | Benefit |
|---|---|
| Deferred transmission | Doesn’t block user requests |
| Edge ingestion | Faster, location-aware event handling |
| Async acknowledgment | Sub-10ms response time |
| Low-level PHP | Minimal CPU overhead |
| Lightweight package | Small install size, fast boot |
Still Have Questions?
Section titled “Still Have Questions?”If you’re curious about Laritor’s performance in your specific stack or traffic model, feel free to reach out: 📬 [email protected]
We’re happy to provide benchmarks, real-world load examples, and guidance on zero-impact monitoring.