quarkus WebSockets Next: performance improvements

WebSockets Next: performance improvements

Open mkouba opened this issue 11 months ago • 31 comments

Follow-up of https://github.com/quarkusio/quarkus/pull/39142.

use an AtomicLongFieldUpdater in the ConcurrencyLimiter: https://github.com/quarkusio/quarkus/pull/39142#discussion_r1510855917

Mar 04 '24 11:03 mkouba

The https://github.com/quarkusio/quarkus/pull/40183 is related to this issue.

Apr 23 '24 10:04 mkouba

For this one, we'll need some benchmarks (executed automatically). Ideally, to compare WS next with quarkus-websockets and pure Vert.x.

CC @franz1981

Jun 25 '24 12:06 mkouba

I'm not aware of websocket benchmark suites sadly...

Jun 25 '24 12:06 franz1981

I'm not aware of websocket benchmark suites sadly...

Me neither. We'll need to come with something... ;-)

Jun 25 '24 13:06 mkouba

Let's talk this week in a call and we can think about something

Jun 25 '24 13:06 franz1981

NOTE: This extension contains a bunch of lambdas. We should consider rewriting those lambdas to anonymous classes.

Jun 27 '24 06:06 mkouba