From e3db94a3b8280b6d0b2ae38f9868a8ff94f89f88 Mon Sep 17 00:00:00 2001 From: lihaoyi Date: Sun, 2 Feb 2025 12:19:31 +0000 Subject: [PATCH] deploy: b27a63e0e232ff793ae22777b16f4c7dd4ada025 --- index.html | 1 + 1 file changed, 1 insertion(+) diff --git a/index.html b/index.html index d149e79f22..2d445dabcb 100644 --- a/index.html +++ b/index.html @@ -1295,6 +1295,7 @@
  • You can change the default scheduler of the carrier threads with cask.internal.Util.createVirtualThreadExecutor method, but keep in mind, that's not officially supported by JDK for now.
  • You can supply your own Executor by override the handlerExecutor() method in your cask.Main object, which will be called only once when the server starts.
  • You can use jdk.internal.misc.Blocker's begin and end methods to help the ForkJoinPool when needed.
  • +
  • You can use Util.createVirtualThreadScheduler to create separate ForkJoinPool as scheduler for the virtual threads.
  • NOTE: