Making sense of latency numbers
The latency numbers every programmer should know, scaled to buildings, cities and states so nanoseconds, microseconds and milliseconds finally feel different.
2 posts tagged “Performance”. All topics.
The latency numbers every programmer should know, scaled to buildings, cities and states so nanoseconds, microseconds and milliseconds finally feel different.
Cutting a Go cron job's peak memory from 16.5 GB to 50 MB with streaming queries, bounded concurrency and a buffered writer.