Timeline for Can multi-threading improve performance of an IO-bound process?
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 3, 2024 at 15:39 | comment | added | Sahil | @StackExchangeSupportsIsrael Could you please explain more. What do you mean by word calculator? I have been using it a lot at work, so you comment might help me a lot there. | |
| Aug 3, 2024 at 10:38 | comment | added | abligh | A couple of misconceptions here: 1. Slow API calls are not in general "I/O" in the sense of "IO Bound" (compare reading/writing to disk) - the network interface is not in general saturated. 2. You can make parallel API calls without multithreading - for instance with an async API, or careful use of select() etc in a single thread, or multiple processes. | |
| Aug 2, 2024 at 9:01 | answer | added | AnoE | timeline score: 0 | |
| Aug 2, 2024 at 6:27 | answer | added | gnasher729 | timeline score: 0 | |
| Aug 2, 2024 at 5:45 | answer | added | Simon Geard | timeline score: 2 | |
| Aug 2, 2024 at 2:27 | comment | added | jmoreno | Async and threads aren’t magic, they always result in more work. More work generally equals more time, but when that extra work is done in an otherwise downtime, the effect is for the process to be faster even though all of the individual pieces take the same or more time. | |
| Aug 2, 2024 at 1:28 | comment | added | Jasen | If chatgpt claimed this then you should ask chatgpt to defend its assertion. | |
| Aug 1, 2024 at 21:40 | history | became hot network question | |||
| Aug 1, 2024 at 17:18 | answer | added | JimmyJames | timeline score: 5 | |
| Aug 1, 2024 at 17:05 | answer | added | Christophe | timeline score: 3 | |
| Aug 1, 2024 at 15:47 | comment | added | user4828 | Yes, that's the idea. When you have a limited resource (network bandwidth for example) simply throwing more requests at it doesn't improve matters. Keep in mind that sending a data packet over the network is a physical process that takes time. You can't make it go faster than the physical constraints of the network allow. | |
| Aug 1, 2024 at 15:33 | comment | added | Sahil | @CharlesE.Grant so waiters are threads, and chef is network IO call like an API call in your analogy? | |
| Aug 1, 2024 at 15:21 | answer | added | candied_orange | timeline score: 2 | |
| Aug 1, 2024 at 15:15 | review | Close votes | |||
| Aug 8, 2024 at 3:04 | |||||
| Aug 1, 2024 at 15:08 | comment | added | user4828 | Think of it this way: if you have a restaurant with one cook and multiple waiters, once the chef is maxed out, adding more waiters won't get the meals on the tables any faster. | |
| Aug 1, 2024 at 15:04 | history | edited | Joris Timmermans | CC BY-SA 4.0 |
Slight clarification of english / spelling errors
|
| Aug 1, 2024 at 14:29 | answer | added | Steve Mathwig | timeline score: 3 | |
| Aug 1, 2024 at 14:26 | answer | added | Kilian Foth | timeline score: 16 | |
| Aug 1, 2024 at 13:48 | answer | added | Caleth | timeline score: 1 | |
| Aug 1, 2024 at 13:45 | answer | added | pjc50 | timeline score: 6 | |
| Aug 1, 2024 at 13:39 | history | asked | Sahil | CC BY-SA 4.0 |