The TMA02 assignment is not about speed. It is about mastery. When you build your own weak instance of NejicomiSimulator, you learn:
There is no cloud. There is no abstraction. There is only your code, your hardware, and the laws of physics. NejicomiSimulator TMA02 - My Own Dedicated Weak...
Why would anyone deliberately build a weak simulator? Modern devs chase teraflops. The TMA02 rubric, however, forces a different mindset. The TMA02 assignment is not about speed
My Own Dedicated Weak means:
This constraint teaches efficiency. You cannot leak memory. You cannot rely on lazy loading. Every byte is sacred. There is no cloud
In the rapidly evolving field of computer science and technology, simulators play a crucial role in the development, testing, and understanding of complex systems. One such intriguing project is the NejicomiSimulator TMA02. This essay aims to explore the concept, significance, and potential implications of creating a dedicated, albeit weak, setup for such a simulator.
The preallocated ringbuffer for particle data (screwed elements) was suffering from internal fragmentation. The solution was to align all structs to 16 bytes and use a custom slab allocator (32 lines of C). After this, the peak memory usage dropped from 412MB to 348MB – fitting under the 384MB cap.