since 2 months ago
13 of 13
Tip Reveddit Real-Time can notify you when your content is removed.
your account history
Tip Check if your account has any removed comments.
view my removed comments you are viewing a single comment's thread.
view all comments
Oh yeah, for sure. From my own rudimentary understanding of Cosmoteer's multithreading, there's a main thread for physics entities, and every ship gets a thread assigned to it that handles all the crew pathfinding
To get such a system to be deterministic though, means you gotta have actions sync between completely separate threads that aren't even interacting with each other. No thread is allowed to run faster than the slowest thread - this is the performance cost
Threads parallelize computations, so syncing actions is threads waiting on multiple threads to finish their jobs. This is still faster than one single thread doing everything in sequence, even if there's waiting involved.
Yes, deterministic multithreading is still faster than singlethreading, but it is still slower than not caring about determinism with multithreading
Yep :)
But then when it comes to actually coding it, I feel like going multithreaded and doing it right would be such a hard task, especially for a team of devs on a large scale project (like Minecraft) that the time needed for it would make the business side reject it at every occasion. Also the boilerplate code that would be necessary to achieve this…
But then I’m jr dev so please correct me if I’m taking out of my ass since it’s not even my side of things
Writing multithreaded code is relatively easy if you write pure functional code. Since FP never updates any values ever, and race conditions always involve writing (write/write or read/write), all those problems are avoided. Since lambda calculus is Turing complete, you can write any program using a purely functional paradigm.
Well yeah I guess if you do purely FP maybe, but then they use Java and not say Haskell.
And I’m not saying that you cannot do FP in Java, but then it’s not what Java was made for, and for some reason they rewrote it in C# (I believe other than that it’s just their creation).
Isn’t bedrock c++? I think a big reason for the rewrite was better performance.
And yeah Java isn’t the best language for FP. But you can definitely write stuff with lees or no mutation if you know you’re going to have to deal with multithreading.
So waterfall but for processor time instead of developer/coder time xD
By the way, not to dogpile on the "I could go do it better with my implementation!!" crowd but my favorite devblog about multithread recently is from Dyson sphere program: https://store.steampowered.com/news/app/1366540/view/534362428708750267
I have no idea if you're right but if so that's a terrible model for multithreading, you want to start with a thread pool that maps directly to the hardware and then manage work distribution on top of that via continuation functions
Immediate mode rendering is also deferred. All rendering is deferred. Immediate mode rendering just means you don't retain UI state but instead build the entire view hierarchy from scratch every frame. So essentially instead of caching a bunch of View objects and syncing their properties with your state and vice versa, you have a script to render the whole UI based off current state as is.