data-oriented-design

One feature that plays a prominent role in many of the writings on data oriented design is that there are many cases where rather than AoS (array of structs): struct C_AoS { int foo; double bar; }; std::vector<C_AoS> cs; ... std::cout << cs[42].foo << std::endl; it is more efficient to arrange one's data in SoA (struct of arrays): struct C_SoA { std::vector<int> foo; std::vector<double> bar; }; C_SoA cs; ... std::cout << cs.foo[42] << std::endl; Now what I am looking for is a solution which would allow me to switch between AoS and SoA without changing the calling interface, i.e. that I could,

I am trying to get a good grip on data oriented design and how to program best with the cache in mind. There's basically two scenarios that I cannot quite decide which is better and why - is it better to have a vector of objects, or several vectors with the objects atomic data? A) Vector of objects example struct A { GLsizei mIndices; GLuint mVBO; GLuint mIndexBuffer; GLuint mVAO; size_t vertexDataSize; size_t normalDataSize; }; std::vector<A> gMeshes; for_each(gMeshes as mesh) { glBindVertexArray(mesh.mVAO); glDrawElements(GL_TRIANGLES, mesh.mIndices, GL_UNSIGNED_INT, 0); glBindVertexArray(0)

I've recently been reading about AoS vs SoA structure design and data-oriented design . It's oddly difficult to find information about either, and what I have found seems to assume greater understanding of processor functionality than I possess. That said, what I do understand about the former topic in particular leads to some questions that I think I should be able to understand the answers to. Firstly, to make sure I am not basing my understanding off of a false premise, my understanding of the functionality and pros and cons of AoS vs SoA, as applied to a collection of 'Person' records with

I was reading this article , and this guy goes on talking about how everyone can greatly benefit from mixing in data oriented design with OOP. He doesn't show any code samples, however. I googled this and couldn't find any real information as to what this is, let alone any code samples. Is anyone familiar with this term and can provide an example? Is this maybe a different word for something else? Erik Engheim First of all don't confuse this with data driven design. My understanding of Data Oriented Design is that it is about organizing your data for efficient processing. Especially with