> you can add fields to your 1M monsters with little impact.

Great for this access pattern, but I wouldn't make a general statement like that. This is the same thing as row-oriented vs column-oriented databases, OLTP vs OLAP. SoA is weak if you are adding/removing monsters more often than accessing a single "hot" field.

▲

Altern4tiveAcc 13 minutes ago | parent | next [-]

> SoA is weak if you are adding/removing monsters more often than accessing a single "hot" field.

Why is that? Genuinely curious. Does "weak" mean that it performs worse than AoS, or that the gains aren't as significant versus AoS?

	▲	jayd16 5 minutes ago \| parent [-]
		Presumably they're referring to resizing the arrays.

▲

keynha 10 minutes ago | parent | prev [-]

[dead]