Skip to content

Commit fe33767

Browse files
committed
Update notes
1 parent b305b05 commit fe33767

File tree

2 files changed

+9
-1
lines changed

2 files changed

+9
-1
lines changed

README.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,7 @@ Simple and easy to understand code examples for most of the Concurrent APIs prov
2222
- [How many subtasks/threads to break the original task into?](./notes/performance-in-multithreading.md#n--)
2323
- [Hyper-threading](./notes/performance-in-multithreading.md#hyper-threading)
2424
- [Inherent cost of Parallelization and Aggregation](./notes/performance-in-multithreading.md#inherent-cost-of-parallelization-and-aggregation)
25+
- [Can we always break any task into multiple subtasks?](./notes/performance-in-multithreading.md#can-we-always-break-any-task-into-multiple-subtasks)
2526
- [Throughput](./notes/performance-in-multithreading.md#throughput)
2627

2728
#### Thread synchronization and locks

notes/performance-in-multithreading.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,4 +70,11 @@ We cannot run all the threads 100% in parallel, but we can get close to that!
7070

7171
### Inherent cost of Parallelization and Aggregation
7272

73-
![Inherent cost of Parallelization and Aggregation](../images/latency_5.png)
73+
![Inherent cost of Parallelization and Aggregation](../images/latency_5.png)
74+
75+
76+
### Can we always break any task into multiple subtasks?
77+
78+
The answer is NO!
79+
80+
- Small and trivial tasks are not worth breaking and running in parallel.

0 commit comments

Comments
 (0)