3 ms·
If you need to do something which was never done because of efficiency problems, you need to think about how to do it before you start. It's called planning, no
by yetihehe 10y ago
If you need to do something which was never done because of efficiency problems, you need to think about how to do it before you start. It's called planning, not premature optimization. Just optimizing existing approaches won't do anything good here as author said in beginning.
- Dzugaru 10y ago> which was never done Highly doubt that. Oh, and when I see a phrase "millions of things interacting" and don't see a word "GPU" anywhere I feel strange. Just saying.
- majewsky 10y agoAssuming that he is talking about a city sim as a game, I can understand that he doesn't want to use the GPU for the simulation, since it will be occupied with the (even more expensive) rendering of the city.
- anselm_eickhoff 10y agoThat and that I really want to avoid having to debug GPGPU code for the main simulation. But I'm not saying it won't become GPGPU at some point!
- ggambetta 10y agoIt is a bit premature in a way; paraphrasing here, but "a million is not cool. You know what's cool? A billion" No matter how much you optimise CPU caches and memory allocators, at some point your application won't fit in a single machine, and you'll have to go distributed. Datacenters, not mainframes :)
- anselm_eickhoff 10y agoBut if you're already using message passing, this transition will be much more natural!