Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
An extensive Maven example: https://github.com/forax/loom-fiber
The Jetty ones use Jex and Loom based Jetty ThreadPool implementation ... and note that this isn't how the Jetty folks themselves have been playing around with Loom (see their loom branch). However, testing this just now against the latest 19 EA in what I think is the worst case scenario for Loom has: Loom at 80 rps and Traditional at 90 rps. Worse case scenario for loom meaning there is NO WAIT AT ALL in the response and that we do not exceed the Traditional Jetty thread pool size (testing at 100 concurrent clients which is less than default 200 max Jetty thread pool). As soon as we introduce IO wait + exceed the traditional thread pool size in terms of concurrent activity is when we see loom win out.