PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Optimizing Your Application for Speed

hackerone.com | blog | #ai-security | #monitoring | #performance | #optimization | #application-speed | #user-experience
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

Nikhil Pal Singh explains why application speed drives retention — each extra second of load time cuts satisfaction by 16% — and outlines tracking and monitoring practices to remove bottlenecks.
Published
Collected

Related coverage

blog · hackerone.com
Optimizing Performance in Generative AI: Trimming Tokens
Output tokens are generated sequentially and dominate LLM latency; trimming verbose inputs, capping output length, and using smaller models or parallelism can greatly improve generative AI performance.
research · blog.quarkslab.com
Convert IPv4 string representation to a 32-bit number with SSE instructions
Converting IPv4 strings to 32-bit integers with SSE intrinsics: benchmarks against libleeloo and inet_aton (~20M conversions/s) and the SIMD parsing tricks that beat conventional implementations.
blog · hackerone.com
Measuring The Fix: How We Evaluate Frontier Models on Remediation Quality
HackerOne tested frontier models on security fix quality and found the judge mattered more than the model. See how CTEM remediation earns engineer trust.
blog · hackerone.com
Lessons Learned from Over a Decade of On-Call
HackerOne engineer Shubhi Gupta distills 12 years of on-call experience into guidance on designing alerts around what, when, who, and why—and how over-alerting erodes response quality.
blog · hackerone.com
Unlocking Performance with Memoization: A Developer's Guide
HackerOne's developer guide to memoization: caching expensive function results for reuse, Python's functools.lru_cache, when the technique applies (limited inputs, costly calls, repeated arguments) and its use beyond individual functions.
blog · hackerone.com
Leveraging Async/Await in ASP.NET for Enhanced Performance
Covers effective async/await usage in ASP.NET: reserve it for I/O-bound work, avoid .Result and .Wait() deadlocks with ConfigureAwait(false), and skip async for CPU-bound paths.
Back