More about locality

In the third post of the memory series we briefly explained locality and why it is an important principle to keep in mind while developing a memory-intensive program. This new post is going inflatable obstacle course to be more concrete and explains what actually happens behind the scene in a very simple example.

This post is a follow-up to a recent interview with a (brilliant) candidate1. As a subsidiary question, we comprar castillo hinchable baratos presented him with the following two structure definitions:

 struct foo_t {
    int len;
    char *data;
 struct bar_t {
    int len;
    char data[];

The question was: what is the difference between aufblasbarer hindernisparcours these two structures, what are the pros and the cons of both of them? For the remaining of the article we will suppose we are working on an x86_64 architecture.

By coincidence, an intern asked more or less at inflatable tent the same time why we were using bar_t-like structures in our custom database engine.

Continue reading

  1. we’re still hiring []