Hacker News new | ask | show | jobs
by UncleEntity 441 days ago
> Author does have a point that slicing the work too small has significant overheads. But they've overstated it.

Exactly.

I was messing around with adding multi-threading to this 3d thing and it slowed it down for the smaller cases up until it overcame the overhead then it sped things up. It was using OpenMP and only a couple shared loop variables so probably not as drastic as whatever node does but it did slow the common case down enough to be not worth the effort.

The author of TFA needs to go run any renderer in single and multi-thread mode then report back to the class.

2 comments

> The author of TFA needs to go run any renderer in single and multi-thread mode then report back to the class.

Indeed. The whole of modern graphics API architecture hinges on the idea that each of your million or so pixels is a meaningful unit of work that can be done in parallel.

I still think that the argument is flawed beyond trivially parallel problems, but my understanding is that the author is arguing for shared-nothing, not for single threaded/single-process solutions.