我也想被裁，反正没房子没孩子。10 万块能用很久很久了。

好

@4771314 确实，而且如果是自己的 feature 分支，最好推送到远端。

还可以开启指针压缩

@junkun 是的，很多开源的集合库可以用。比如 eclipse collection 。

24 年才会替换 JBR 到 jdk 21 吗

直接申明成 var

宜昌吗，可以招我过去吗

@arloor
some blocking operations in the JDK do not unmount the virtual thread, and thus block both its carrier and the underlying OS thread.

If a virtual thread performs a blocking operation such as I/O or BlockingQueue.take() while it is pinned, then its carrier and the underlying OS thread are blocked for the duration of the operation. Frequent pinning for long durations can harm the scalability of an application by capturing carriers.


补充一个，堆大小为 128M：
Time: 
2023-09-20 11:13:18
Used: 108,544 kbytes
Committed: 131,072 kbytes
Max: 131,072 kbytes
GC time: 
 8.149 seconds on ZGC Minor Cycles (384 collections)

 0.006 seconds on ZGC Minor Pauses (1,185 collections)

12.133 seconds on ZGC Major Cycles (61 collections)

 0.001 seconds on ZGC Major Pauses (279 collections)

@voidmnwzp
你说的是这个吧
There are two scenarios in which a virtual thread cannot be unmounted during blocking operations because it is pinned to its carrier:

When it executes code inside a synchronized block or method, or
When it executes a native method or a foreign function.

官方解释：
The scheduler does not compensate for pinning by expanding its parallelism. Instead, avoid frequent and long-lived pinning by revising synchronized blocks or methods that run frequently and guard potentially long I/O operations to use java.util.concurrent.locks.ReentrantLock instead. There is no need to replace synchronized blocks and methods that are used infrequently (e.g., only performed at startup) or that guard in-memory operations. As always, strive to keep locking policies simple and clear.

后续优化：
In a future release we may be able to remove the first limitation above, namely pinning inside synchronized. The second limitation is required for proper interaction with native code.

@Goooooos
JEP 446 Scoped Values (Preview)
Introduce scoped values, values that may be safely and efficiently shared to methods without using method parameters. They are preferred to thread-local variables, especially when using large numbers of virtual threads. This is a preview API.

@Mirage09 升级到 11 了，据说后面再升级就容易了。

这次新版本的新特性还是很值得期待的。虚拟线程和分代 ZGC

分代 ZGC 没人关注吗

@Goooooos https://openjdk.org/jeps/444

irtual threads support thread-local variables (ThreadLocal) and inheritable thread-local variables (InheritableThreadLocal), just like platform threads, so they can run existing code that uses thread locals.

没看到说有优化

我看到油管的信息，分代 ZGC 吞吐量是 ZGC 的四倍，堆大小是 ZGC 的五分之一，很期待。

分代 ZGC 据说性能很强