Separation of draw-loop and update-loop threads. Possible?

[AndreyMust19]

If us running in same thread, then drawing may slows updating and reversal.
Love2d have threads, but is isolated threads, no shared environment, with exchanging by messages. Is possible separate loops to updating and drawing same objects from different threads, to optimal execution on multi-core systems?

[Robin]

Maybe? I think it'll be a lot of work for a small pay-off (if it even has a pay-off), though.

[DaedalusYoung]

I haven't got a lot of knowledge about this, but I'm thinking it wouldn't work, because love.update needs to be finished before love.draw anyway. You don't want to draw anything before its location is updated, if both functions run virtually at the same time.

[Plu]

This sounds to me like it's in the category of "If you have to ask, you don't understand well enough to make it work".

It's going to be a huge undertaking for probably no gain and loads of really weird bugs.

[T-Bone]

Isn't it much easier to just use a fairly minimal love.update-function and put all the heavy lifting of update logic in a different thread? That way you don't have to change everything so much yet you get basically the same result.

[Robin]

The difficulty with that is that you're going to have a lot of traffic between threads to facilitate that, because both the drawing thread and the updating thread need to access a lot of the same data. For a simple game it's no problem, but it just doesn't scale.

[Jasoco]

Would "diminishing returns" be an appropriate name for it? Too much work for such little benefit if any at all.