Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.

We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.

What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.

Your mileage may vary. Batteries not included.

Testing Memory Allocators: ptmalloc2 vs tcmalloc vs hoard vs jemalloc While Trying to Simulate Real-World Loads

July 4, 2018 by “No Bugs” Bunny

Testing Memory Allocators: ptmalloc2 vs tcmalloc vs hoard vs jemalloc While Trying to Simulate Real-World Loads - Post preview image

Quote:

if you DO want to get performance from changing mallocs, make sure to test them with your own app

Another Quote:

in our humble opinion, overall winner so far (by a nose) is jemalloc.

Filed under: On.ProgrammingOptimizations

Read more

The Curse of External Fragmentation: Relocate or Bust!

June 21, 2018 by “No Bugs” Bunny

The Curse of External Fragmentation: Relocate or Bust! - Post preview image

Quote:

We won’t ever get (almost) any virtual memory back, plain and simple

Another Quote:

relocation allows not only to reduce fragmentation, but to eliminate it entirely.

Filed under: On.ProgrammingOptimizations

Read more

How to consume an HTTP API

June 11, 2018 by “No Bugs” Bunny

How to consume an HTTP API - Post preview image

Quote:

Programs are not the self-contained, self-reliant, self-sufficient things they once were.

Another Quote:

I highly recommend you log every HTTP request you send and every HTTP response you receive.

Filed under: On.ProgrammingTips and Tricks

Read more

Unchecked Exceptions for C++

June 7, 2018 by “No Bugs” Bunny

Unchecked Exceptions for C++ - Post preview image

Quote:

‘unchecked’ std::errors are treated as ‘something which should never ever happen, but in practice MAY occur as a result of potentially-recoverable bug'

Another Quote:

Failing-Fast does NOT mean we should necessarily Fail-Hard(!). In certain (production!) cases, Failing-Fast-AND-Soft IS a substantially better alternative.

Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingProgramming LanguagesOn.DevelopmentDevelopment Philosophy

Tagged With: C/C++
Read more