Peter Veentjer (@peterveentjer) 's Twitter Profile
Peter Veentjer

@peterveentjer

Performance engineer @ Adapative, ex-Scylla, ex-Hazelcast.

ID: 1926559184

linkhttps://pveentjer.github.io/ calendar_today02-10-2013 11:17:25

2,2K Tweet

2,2K Followers

196 Following

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

Ad posted on LinkedIn messages; what a terrible idea. The content generally is terrible with all the self proclaimed guru's, but this increases the level of spam even further.

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

A load generator can only properly deal with coordinated omission, if the latency is determined based on the scheduled starting time and not the actual starting time.

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

In Java, when final will mean final, it will cause networking code to create litter. Because the Selector hack to replace the litter producing hashset by something that doesn't produce litter, won't work any longer. Netty and Aeron are some projects that apply this trick.

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

It has been more than a decade I have used aspect-oriented programming, but with ByteBuddy it is pretty sweet. Working on an Aeron async-profiler agent for latency profiling and an Aeron HdrHistogram agent for latency tracking over time.

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

Software engineers should not be concerned about AI replacing their jobs (for now) unless they are performing extremely trivial tasks. I have paid accounts for ChatGPT and Claude, and although it can be useful, AI is typically on massive amounts of LSD.

Peter Veentjer (@peterveentjer) 's Twitter Profile Photo

The more I work with AI (both ChatGPT and Claude) the less I believe engineers should be worried to be replaced unless they are doing extremely trivial work.

Venkat Raman (@venkat2811) 's Twitter Profile Photo

Huge thanks to Peter (Performance Engineer from Adaptive) for spotting a coordinated omission issue in my benchmark. His feedback was spot on. (See Gil Tene's 'How NOT to Measure Latency' for a deep dive on this). My original test showed peak throughput. This CO-corrected

Huge thanks to Peter (Performance Engineer from <a href="/WeAreAdaptive/">Adaptive</a>) for spotting a coordinated omission issue in my benchmark. His feedback was spot on. (See Gil Tene's 'How NOT to Measure Latency' for a deep dive on this).

My original test showed peak throughput. This CO-corrected