Breaking the monolith – How to design your system for both flexibility and scale – Part 5: The Common

Adam Lev-Libfeld

A long distance runner, a software architect, an HPC nerd (order may change).

Latest posts by Adam Lev-Libfeld (see all)

This post is part of a series. you’d probably like to read it from the beginning. Or check out the previous post in the series

One of the ways to boost performance is ruthless consolidation and parallelization of your critical sections (these are the parts of you system that does the heavy lifting). For that to happen you need to figure out a rule of thumb for each of those “heavy lifting” processes or what actions are common to the processing of input you may encounter.

Continue reading “Breaking the monolith – How to design your system for both flexibility and scale – Part 5: The Common”

Breaking the monolith – How to design your system for both flexibility and scale – Part 5: The Common

Tracing Python memory leaks

Adam Lev-Libfeld

A long distance runner, a software architect, an HPC nerd (order may change).

Latest posts by Adam Lev-Libfeld (see all)

… It’s not so easy for a Python application to leak memory. Usually there are three scenarios …

Source: LShift – Tracing Python memory leaks

Just used the method in this article to solve a stochastic app crush problem for a client. How would imagine setting some global variables is more than just typing global in random places around your code base.

Link