Thread Safety for Shared Resources

[tmt1]

I was just thinking of the first concurrency problem I encountered whereby you have multiple threads incrementing a shared variable ('int x').

Now, I understand the problem and how it is solved, but since int x is a shared resource only one thread can access it at a time, so no time at all is saved. So all the concurrency problems for shared resources won't save time they will just allow concurrent tasks, whereas you can save time by increasing the number of tasks for non-shared resources?

 

[Future Bruno]

Yes, that is correct. When dealing with shared resources, the main benefit of introducing concurrency is to allow multiple tasks to be executed concurrently. This can result in improved overall throughput, but it does not necessarily result in faster task execution times. In contrast, when dealing with non-shared resources, multiple tasks can be executed in parallel, which can result in faster task execution times.