- Learning Concurrency in Kotlin
- Miguel Angel Castiblanco Torres
- 100字
- 2021-08-05 10:46:42
Concurrency versus parallelism in I/O-bound algorithms
As seen before, I/O-bound algorithms are constantly waiting on something else. This constant waiting allows single-core devices to use the processor to do other useful tasks while waiting. So concurrent algorithms that are I/O-bound will perform similarly regardless of the execution happening in parallel or in a single core.
It is expected that I/O-bound algorithms will always perform better in concurrent implementations than if they are sequential. So it's recommended for I/O operations to be always executed concurrently. As mentioned before, in GUI applications it's particularly important to not block the UI thread.
推薦閱讀
- The React Workshop
- Java面向?qū)ο蟪绦蜷_發(fā)及實戰(zhàn)
- 精通Linux(第2版)
- Python程序設(shè)計與算法基礎(chǔ)教程(第2版)(微課版)
- Django Design Patterns and Best Practices
- Software-Defined Networking with OpenFlow(Second Edition)
- JavaEE架構(gòu)與程序設(shè)計
- 從“1”開始3D編程
- 軟硬件綜合系統(tǒng)軟件需求建模及可靠性綜合試驗、分析、評價技術(shù)
- 從零開始學(xué)Unity游戲開發(fā):場景+角色+腳本+交互+體驗+效果+發(fā)布
- RESTful Web API Design with Node.js
- 絕密原型檔案:看看專業(yè)產(chǎn)品經(jīng)理的原型是什么樣
- Mathematica Data Visualization
- Visual FoxPro程序設(shè)計
- Getting Started with SpriteKit