4 ms·
These are good tips but I would also add that if you can avoid shared memory altogether, then you should avoid it. If you can shard and distribute the data nea
by cryptica 7y ago
These are good tips but I would also add that if you can avoid shared memory altogether, then you should avoid it.
If you can shard and distribute the data neatly and evenly so that each process handles a completely separate subset, then that is the most reliable long term solution.
With shared memory, it's difficult to control who has access to what parts and when - and that can make it difficult to detect and analyse bottlenecks.