Skip to Content

Changes for page Concurrency

Last modified by chrisby on 2024/06/02 15:15
From version 1.18
edited by chrisby
on 2023/11/30 21:26
Change comment: There is no comment for this version
To version 1.19
edited by chrisby
on 2023/11/30 21:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -49,5 +49,4 @@
49 49  * **Performance**: When a performance bottleneck is detected in an application, the cause can be I/O or CPU. Increasing the number of threads will show which of the two is the actual bottleneck, see [[this article|doc:Software Engineering.Testing.Enhance Test Execution Speed.WebHome]].
50 50  * **Stress Testing**: A common type of test that determines the maximum throughput of an application by sending a large number of requests and examining the response times.
51 51  * **Execution Paths**: Always consider the concept of different execution paths. The amount of possible interleaving of instructions that are processed by at least two threads. For example, objects with mutable states could unintentionally cause different results doing the same operation twice.
52 -*
53 53  * **Write Shutdown Code Early**: Shutting down an application requires the safe termination of all concurrent processes. Writing shutdown code is difficult. Writing shutdown code early is cheaper than writing it later. Study the available algorithms.