课程: Java Concurrency Troubleshooting: Latency and Throughput

今天就学习课程吧！

今天就开通帐号，24,700 门业界名师课程任您挑！

Bad component defaults

Bad component defaults - Java教程

课程: Java Concurrency Troubleshooting: Latency and Throughput

开始一个月试用 购买团队方案

Bad component defaults

“

- {instructor] In the serverless and microservice world, it's awfully tempting to just bootstrap a project, plunk your code in it, and it's runtime baby, or is it? See in the world of convention over configuration and "sensible defaults" We allow these frameworks to make good-intentioned assumptions on our behalf. Sometimes those assumptions don't pan out in our favor. No, what they will do is quietly slow down the application death by a thousand cuts. These types of bottlenecks are particularly nefarious because they don't manifest as a bright flashing red sign screaming bottleneck here. No, it's a bunch of quiet slowdowns peppered all over the application like a lot of R&B music. In some scenarios, the defaults won't do. Take garbage collection for example. The JVM makes some assumptions on your behalf based on the amount of RAM a detects on your machine. By default, it'll attempt to reserve about 25% of your RAM. 1/4 of…

内容