wangzhigang1999 commented on PR #7656:
URL: https://github.com/apache/kyuubi/pull/7656#issuecomment-5409956237

   I finished a larger benchmark on JDK 25, limited to the server-side 
`TBinaryFrontendService` change in this PR. The test included 32 runs, each 
with a 60-second warm-up and a 300-second measurement window.
   
   In the 10,000-connection capacity test, virtual threads reduced the Kyuubi 
Server OS thread count from 10,053 to 56, NMT thread committed memory from 
971.4 MiB to 5.1 MiB, pod peak memory from 1,653.8 MiB to 947.7 MiB, and RSS 
from 1,217.5 MiB to 888.4 MiB. Binary RPC performance remained close overall, 
and real Spark SQL showed no meaningful regression. All 16 virtual-thread JFR 
recordings reported zero `jdk.VirtualThreadPinned` events on JDK 25.
   
   Since JEP 491 was delivered in JDK 24, these results do not cover 
`synchronized` pinning behavior on JDK 21. Do you think we should run a 
separate JDK 21 comparison before recommending this option on JDK 21 runtimes?
   
   - [English 
report](https://doctor-pre.cn-hangzhou.oss.aliyuncs.com/zhigang%2Fkyuubi-vt-bench%2Fserver-binary-virtual-threads-jdk25-spark42%2F2026-08-25%2FBENCHMARK_REPORT.md?Expires=2103277634&OSSAccessKeyId=LTAI5tHZK1BGMUmnYHFDpmcK&Signature=UB96qFkLwaBZZ%2Fwsr6pSG3GtUJc%3D)
   - [Chinese 
report](https://doctor-pre.cn-hangzhou.oss.aliyuncs.com/zhigang%2Fkyuubi-vt-bench%2Fserver-binary-virtual-threads-jdk25-spark42%2F2026-08-25%2FBENCHMARK_REPORT_ZH.md?Expires=2103277634&OSSAccessKeyId=LTAI5tHZK1BGMUmnYHFDpmcK&Signature=27FOqyyY0TZqXyL2M2LyoV%2BXOH8%3D)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to