After few days studying how go and other runtimes implements work-stealing the Loom custom scheduler - I've built a new one for @netty_project (but can be used with any transport you like as #aeron or #dpdk..) on locality-first principles, see github.com/franz1981/Netty-V… (1/2)

Been working on picocli to aesh migration the last few weeks for JBang. The startup difference is amazing - 2-17x faster. JVM mode is now amazing but native mode is even faster lesson learned again and again - reflection is a startup killer; build-time makes all the difference

"Why does our top performer get the worst reviews?" the boss asked. I was reviewing their annual performance data. "Show me," I said. She pulled up the ratings. Diana: 2.8 out of 5. Below average on "collaboration." Low marks for "team player." "What's her actual performance?" I asked. "Exceeded every target. Landed our biggest client. Trained three new hires." "So why the low scores?" "Her peer reviews are dragging her down." I scanned the comments. "Too direct." "Challenges ideas too much." "Not supportive enough." "Let me talk to Diana," I said. "I used to give honest feedback," Diana told me. "Said our pricing model was broken. Got dinged for 'negativity.'" "What happened with the pricing?" "They finally fixed it six months later. After we lost two major accounts." "What else?" "I questioned why we needed eleven approvals for a simple contract change. Manager said I wasn't being collaborative." "Are you still giving feedback?" "No. I learned my lesson. Now I smile. Nod. Say everything's great. My reviews are improving." "But nothing's actually improving?" "We're making the same mistakes. Just with better vibes." She chuckled. I went back to the boss. "Your review system doesn't measure performance," I said. "It measures compliance." "That's not true." "When was the last time someone got promoted for challenging bad ideas?" Silence. "When did someone get rewarded for preventing a mistake?" More silence. "You've trained your best people to stay quiet. And your mediocre people to stay nice." A few months later, they redesigned the system. Added a category: "Constructive Challenge." Points for identifying problems early. Rewards for preventing costly mistakes. Diana got promoted. "What changed?" I asked the boss. "We stopped confusing agreement with alignment. Stopped mistaking silence for harmony." "And?" "Turns out our 'difficult' people were our most valuable. They actually cared enough to speak up." Here's the truth about performance reviews: Most companies don't reward performance. They reward performance theater. The person who says the meeting was great beats the person who says it wasted an hour. The person who agrees with bad ideas beats the person who prevents disasters. You think you're measuring contribution. You're measuring conformity. And your best people? They've already figured out the game. They're just deciding whether to play it or find somewhere that values truth over comfort.

Struggling with Java scalability in containers? 🧐 The App Services Performance Team explains how tiered compilation and CPU resource constraints can cause performance bottlenecks! #Java #Performance #Kubernetes #OpenJDK #Scalability 👇 redhatperf.github.io/post/me…

Struggling with unreproducible performance testing? Discover how we leveraged qDup,a powerful scripting orchestrator, to achieve consistent and comparable setups, transforming collaboration and improving our process. Read more about our journey here 👉 redhatperf.github.io/post/su…

Another excellent article from the IBM Runtimes Perf team covering how we used qdup to ensure we could reproduce perf tests between teams in different companies; redhatperf.github.io/post/su… #performance #automation

🗓️ Giovedì 20 Febbraio 2025 👉 "An accidental conspiracy: how your load generator is lying to you" in presenza e YouTube live! 🙏 presenta Andrea Lamparelli Hybrid mode: 🚨 per partecipare in presenza: eventbrite.com/e/an-accident… ⚠️ Dettagli: jugmilano.it/meeting-161.htm…

youtube.com/watch?v=dCryQg7C… Dear @Devoxx thanks for this, I really hope people which love #benchmarking and #performance, but normal devs as well, will have something to learn and fun with it 🥰

"Lets just do 30 minutes" was what Josh Long said but once we got started it took a bit more. Go watch Josh and I's conversation about JBang this early Sunday morning. buff.ly/3ZMGFX8

I am pretty proud of bugs.openjdk.org/browse/JMC-… since I've modelled this index on what garbagecat does and is very useful when #openshift limits doesn't allow to run with proficiency #java concurrent GCs

Premature abstraction is WAY more prevalent and worse than premature optimization and really handcuffs code bases for years and years.

legendary

Lucky to experience another tool concert!!!

Quarkus Insights #166: Lies, Damn Lies...and Techempower(?) x.com/i/broadcasts/1lDxLPyZL…

so this triggered a chat with @forked_franz , @JohnnyDoItAll and @stalep and now you can do: jbang wrk2@hyperfoil -t2 -c100 -d30s -R 200 --latency http://localhost:8080/api/test Hyperfoil backed wrk2 styled test runs. Now...what about that java dsl :)

"this is how we do it" the @QuarkusIO and MW performance team way

I've been reverse engineering the xz backdoor this weekend and have documented the payload format and written a proof-of-concept exploit for the RCE. The payloads are signed with an ED448 key, so I patched my own key into the backdoor for testing. :-) github.com/amlweems/xzbot

github.com/openjdk/jdk/pull/… by @RedHat 's @AndrewHaley13 Bye bye type pollution issue, you won't be missed!