|
You are here |
blog.jcoglan.com | ||
| | | | |
sookocheff.com
|
|
| | | | | Writing correct programs is hard; writing correct concurrent programs is harder. Java Concurrency in Practice. So, why bother with concurrency? A number of reasons: Concurrency provides a natural method for composing asynchronous code. Concurrency allows your program to avoid blocking user operations. Concurrency provides one of the easiest ways take advantage of multi core systems. As processor counts increase, exploiting concurrency will be an even more important facet of high performance systems. | |
| | | | |
clojure-doc.org
|
|
| | | | | This guide covers: | |
| | | | |
lenholgate.com
|
|
| | | | | [AI summary] The author discusses performance tuning techniques for a server framework, comparing lock-free allocators with a new multi-pool locking strategy to reduce thread contention. | |
| | | | |
8thlight.com
|
|
| | | [AI summary] The article by Robert C. Martin (Uncle Bob) discusses the strategic use of mock objects in software testing, advocating for a balanced approach where mocks are used sparingly across architectural boundaries to improve test speed and isolation while avoiding design damage. | ||