/explore
|
You are here 
|
mazzo.li | ||
| | | | |
ravendb.net
|
|
| | | | | I previously askedwhat the code below does, and mentioned that it should give interesting insight into the kind of... | |
| | | | |
www.lukas-barth.net
|
|
| | | | | If you build an application that uses large, contiguous amounts of memory, it can increase your performance if you allocate this memory in so-called huge pages. Linux offers you two ways of doing that - a legacy way and a modern way. This article describes the modern way of using huge pages, so called transparent huge pages (THP) and applies the techniques from a previous article to verify that we actually got huge pages. The article starts by giving a super-short recap on how paging works and why huge p... | |
| | | | |
rigtorp.se
|
|
| | | | | In this article I will explain when and how to use huge pages. | |
| | | | |
jmmv.dev
|
|
| | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | ||
