3 citations · 9 across the 6 of their papers we have counts for
6 papers
Who Ate My Memory? Towards Attribution in Memory Management
Gunnar Kudrjavets, Ayushi Rastogi, Jeff Thomas +1
To understand applications' memory usage details, engineers use instrumented builds and profiling tools. Both approaches are impractical for use in production environments or deplo…
When malloc() Never Returns NULL -- Reliability as an Illusion
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
For decades, the guidance given to software engineers has been to check the memory allocation results. This validation step is necessary to avoid crashes. However, in user mode, in…
There Ain't No Such Thing as a Free Custom Memory Allocator
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
Using custom memory allocators is an efficient performance optimization technique. However, dependency on a custom allocator can introduce several maintenance-related issues. We pr…
Is Kernel Code Different From Non-Kernel Code? A Case Study of BSD Family Operating Systems
Gunnar Kudrjavets, Jeff Thomas, Nachiappan Nagappan +1
Code churn and code velocity describe the evolution of a code base. Current research quantifies and studies code churn and velocity at a high level of abstraction, often at the ove…
The Evolving Landscape of Software Performance Engineering
Gunnar Kudrjavets, Jeff Thomas, Nachiappan Nagappan
Satisfactory software performance is essential for the adoption and the success of a product. In organizations that follow traditional software development models (e.g., waterfall)…
Quantifying Daily Evolution of Mobile Software Based on Memory Allocator Churn
Gunnar Kudrjavets, Jeff Thomas, Aditya Kumar +2
The pace and volume of code churn necessary to evolve modern software systems present challenges for analyzing the performance impact of any set of code changes. Traditional method…