Issue #

Using separate arrays instead of an Array-of-Structs is recommended to maximize locality of reference.

Relevance #

Using an Array-of-Structs (AoS) leads to inefficient use of the memory subsystem unless data from all of its fields is used. One example case where using an AoS is justified would be iterating over an array of points, each point being a struct containing the coordinates that are consumed on each iteration. However, most structs contain fields that will not be accessed every time: data locality can be enhanced by breaking the struct and creating an array for each individual field.

Actions #

Convert the Array-of-Structs (AoS) into separate plain arrays.

Code example #

The following example shows a loop processing the x and y coordinates for an array of points:

typedef struct {
   int x;
   int y;
   int z;
} point;
 
void foo() {
   point points[1000];
   for (int i = 0; i < 1000; i ++) {
       points[i].x = 1;
       points[i].y = 1;
   }
}

This could seem like an example where using an Array-of-Structs is justified. However, since the z coordinate is never accessed, the memory subsystem is not used optimally.  This could be avoided by creating one array for each coordinate:

void foo() {
   int points_x[1000];
   int points_y[1000];
   int points_z[1000];
   for (int i = 0; i < 1000; i ++) {
       points_x[i] = 1;
       points_y[i] = 1;
   }
}

Related resources #

• PWR016 examples at GitHub

References #

• AoS and SoA