With 64 bit address spaces, thread stacks should have GBs reserved by default, and programming with alloca should be encouraged. A lot of string and container work could be done at high performance with alloca and no frees if you don't let them escape.
-
In my experience, if you are trying to make sure your cores are working all the time, you want to get rid of as many sync points as possible. Sync points around something common like allocation are death, threads will logjam there very quickly.
But one may not notice this if one is not profiling threads with an eye to maximizing performance.
-
-
Passing memory between threads is annoying if the originating thread has to free it. But under this model, where nobody explicitly frees the memory (except the per-frame reset), there is no problem passing it between threads.
-
That’s the whole idea. That memory is transient and only lives for one frame. Allows to break your frame in many small jobs going wide, allowing you to much better balance your thread utilization. This is the model we used back on the PS3 with all the SPUs.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.