How does a circularBuffer improve performance vs competing for a particular memory address(mutex suspends the other)? [closed]

StackOverflow https://stackoverflow.com/questions/18320405

Question

In theory memory circularBuffer sounds like a good idea... the setting and the getting are never at the same address. However the limiting factor in the hardware. The computer will only allow use to access one memory location at a time. So then how can a circularBuffer improve performance ??

Was it helpful?

Solution

This link gives some reasons why circular buffers offer better performance than synchronized access to a single, shared data structure.

What hardware are you using, that only allows access to one memory location at a time?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top