Explore >> Select a destination
|
You are here 
|
letitcrash.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. | |
| | | | |
rcoh.me
|
|
| | | | | Many seasoned engineers working in JVM based languages have seen errors like this: [error] (run-main-0) java.lang.OutOfMemoryError: unable to create native thread: [error] java.lang.OutOfMemoryError: unable to create native thread: [error] at java.base/java.lang.Thread.start0(Native Method) [error] at java.base/java.lang.Thread.start(Thread.java:813) ... [error] at java.base/java.lang.Thread.run(Thread.java:844) OutOfMemory...err...out of threads. On my laptop running Linux, this happens after a paltry 11500 threads. If you try the same thing in Go by starting Goroutines that sleep indefinitely, you get a very different result. | |
| | | | |
piotr.westfalewicz.com
|
|
| | | | | Monitoring services is crucial, if you care about the application uptime. There are hundreds if not thousands parameters which you can (and should) monitor, related to CPU, network, hosts, application and so on. What are they? What are the non-obvious choices? | |
| | | | |
www.snell-pym.org.uk
|
|
| | | |||
