Remove Benchmarking Remove Java Remove Programming Remove Speed
article thumbnail

SKP's Java/Java EE Gotchas: Clash of the Titans, C++ vs. Java!

DZone

This begins not only in designing the algorithm or coming out with efficient and robust architecture but right onto the choice of programming language. Recently, I spent some time checking on the Performance (not a very detailed study) of the various programming languages. JAVA SOLUTION (Will Be Uploaded Later). Ahem, Slow!

Java 207
article thumbnail

Kubernetes Observability: Code Profiling With Flame Graphs

Percona

The idea behind this is to speed up cluster resources such as garbage collection, reduce image transfer over the network, and accelerate the application launch. The documentation mentions that the supported languages to profile are Go, Java (any JVM-based language), Python, Ruby, and NodeJS.

Code 112
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Web Performance Bookshelf

Rigor

Yet, we wanted to put together our list of the top web performance books for anyone who cares about speed of the web and would like to explore the timeline of web performance engineering milestones over nearly two decades through the lens of published books. Site speed & SEO go hand in hand. Speed Up Your Site. Still good.

article thumbnail

The Speed of Time

Brendan Gregg

Was there some other program consuming CPU, like a misbehaving Ubuntu service that wasn't in CentOS? There's no Java stack—there should be a tower of green Java methods—instead there's only a single green frame or two. This is how Java flame graphs looked at the time. 30.14% in the middle of the flame graph.

Speed 126
article thumbnail

The Speed of Time

Brendan Gregg

Was there some other program consuming CPU, like a misbehaving Ubuntu service that wasn't in CentOS? There's no Java stack—there should be a tower of green Java methods—instead there's only a single green frame or two. This is how Java flame graphs looked at the time.

Speed 52
article thumbnail

Static Analysis of Java Enterprise Applications: Frameworks and Caches, the Elephants in the Room

The Morning Paper

Static analysis of Java enterprise applications: frameworks and caches, the elephants in the room , Antoniadis et al., Being static , it has the advantage that analysis results can be produced solely from source code without the need to execute the program. PLDI’20. Why is static analysis of enterprise apps so hard?

Java 80
article thumbnail

The Speed of Time

Brendan Gregg

Was there some other program consuming CPU, like a misbehaving Ubuntu service that wasn't in CentOS? There's no Java stack—there should be a tower of green Java methods—instead there's only a single green frame or two. This is how Java flame graphs looked at the time. 30.14% in the middle of the flame graph.

Speed 40