InfoQ Homepage Performance Tuning Content on InfoQ
-
Uber's Engineering Manages to Cut 70k CPUs by Tuning Go GC
In an effort to help the company become profitable, Uber’s engineering department has focused their efforts on making their infrastructure more efficient. As an outcome of this effort, they managed to develop a semi-automated GO Garbage Collection tuning mechanism which in turn saved 70K CPU cores across 30 mission critical services.
-
Amazon Elasticsearch Service Introduces Auto-Tune
Amazon has recently announced the Auto-Tune feature in Amazon Elasticsearch Service, a closed-loop control system that adapts the Elasticsearch cluster to the running workload. The new automated memory management provides better ingestion throughput for log analytics workloads and reduced tail latencies for search queries.
-
.NET 5 Runtime Improvements: from Functional to Performant Implementations
During a no-slides presentation at .NET Conf 2020, software architects from the .NET runtime team presented several .NET 5 runtime improvements and how they achieved them, including ARM64 support, HTTP/3, and single-file applications.
-
Network Automation at Fastly
Ryan Landry, the senior director for TechOps at Fastly, has shared how network automation enables them to manage traffic peaks during popular live-streamed events such as the Super Bowl LIV. Fastly is directly connected to numerous ISPs across the US and tries to keep their live video traffic on these direct paths with their partners to deliver video streams as close to the end-user as possible.
-
Improving .NET Performance by Reducing Memory Usage
A persistent myth in .NET is that memory allocations don’t affect performance. In this report we take a look at the source of that myth and offer advice on how to reduce memory usage.
-
Q&A with Kyle Mathews, Creator of React-Based Static Site Generator Gatsby
The React-based static site generator, Gatsby, has reached version 1.0. In this interview, founder Kyle Mathews discusses the project's motivations, and how it's going to move forward.
-
Google Retires Octane JavaScript Benchmark
Google has retired their Octane JavaScript benchmark tool, citing over-optimization of micro-benchmarks to the detriment of real-world performance. Other browser vendors agree that the benchmark by itself is of little value. In the future, performance improvements may come from focusing on what the user is actually experiencing.
-
Swift Memory Ownership Manifesto
According to Chris Lattner, Swift creator and Swift team lead before moving to Tesla, defining a Rust/Cyclone-inspired memory ownership model is one of the main goals for Swift development. Now that Swift 4 has entered its phase 2, the Swift team has published a manifesto detailing how Swift memory ownership could work.
-
JavaOne 2016 - Day 1 Highlights
Day 1 of JavaOne 2016 topics: learning about Java 8&9 features, Docker for Java developers, and development tools for Java EE 8. InfoQ highlights a few of the day's interesting sessions.
-
How and Why Etsy Moved to an API-First Architecture
At QCon New York 2016, Etsy software engineer Stefanie Schirmer told how her company successfully transitioned to an API-first architecture that supports multiple devices, addresses server-side performance problems, and was quickly adopted by development teams.
-
Android N Combines AOT, Interpretation and JIT
Android N introduces a hybrid runtime using compilation + interpretation + JIT to obtain the best compromise between installation time, memory footprint, battery consumption and performance.
-
jClarity Releases Censum 3.0
Censum, the Java garbage collection analysis tool by jClarity, has reached version 3.0. The main new features of the new version include the ability to analyse Safepoint logs, new graphs showcasing the behaviour of the G1 garbage collector, and a set of analytics to highlight whenever applications force to much OS activity.
-
Rico Mariani on Why Visual Studio Isn’t 64-bit
For a long time now developers have been asking why Visual Studio hasn’t made to switch to 64-bit. Rather than effort or opportunity cost, the primary reason is performance. Rico Mariani of Microsoft explains.
-
Optimizing Distributed Queries in Splunk
Optimizing queries in Splunk’s Search Processing Language is similar to optimizing queries in SQL. The two core tenants are the same: Change the physics and reduce the amount of work done. Added to that are two precepts that apply to any distributed query.
-
Hunk/Hadoop: Performance Best Practices
When working with Hadoop, with or without Hunk, there are a number of ways you can accidentally kill performance. While some of the fixes require more hardware, sometimes the problems can be solved simply by changing the way you name your files.