Hi, another quick update regarding the TechEmpower benchmark(eting) contribution. While the final blog post is yet to come, the benchmark data is already available (1), and overall pekko-http got a decent overall score, ending up somewhere in the middle of the field (slightly above Akka of course :). The screenshot attached shows maximum RPS for the following test types (2): JSON: 197k, 1-query: 141k, 20-query: 10.5k, Fortunes: 96k, Updates: 1.8k and Plaintext: 2.6M.
(1) https://www.techempower.com/benchmarks/#hw=ph&test=composite§ion=data-r22 (2) https://github.com/TechEmpower/FrameworkBenchmarks/wiki/Project-Information-Framework-Tests-Overview If we wanted to improve the score, there's for sure some low-hanging fruit, including fixing unreasonable parallelism on the DB updates test (multiple parallel update queries for each request without any transactional context) which I intentionally didn't touch because my primary goal was a direct comparison to the Akka implementation. After that I would kindly ask the project to take over the annual polishing, including upgrades and fixes. Cheers, Oliver Am Mo., 4. Sept. 2023 um 08:46 Uhr schrieb Oliver Trosien < o...@pocket-design.de>: > Hi, > > quick update: pekko-http got merged into the test suite (1), and a first > preliminary test round (2) shows it's on par with akka-http (as expected - > we didn't change the logic of the code itself). I'll post another update > when the final numbers are ready. > > Oliver > > (1) > https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/Scala/pekko-http > (2) > https://www.techempower.com/benchmarks/#section=test&runid=074e8a70-d6fb-4f10-82f3-43e57c0965b5&test=json&l=zik0zj-35b&hw=ph&p=zik0z3-zik0zj-zik0zj-zik0zj-v2qiv3-1 > > Am Mi., 23. Aug. 2023 um 14:57 Uhr schrieb PJ Fanning <fannin...@gmail.com > >: > >> I think we should be able to keep track of this in future. >> >> On Wed, 23 Aug 2023 at 13:20, Oliver Trosien <o...@pocket-design.de> >> wrote: >> > >> > Hi PJ, >> > >> > sure, I can do the initial submission. My main point is that it only >> makes >> > sense if the project is willing to take over the long-term maintainence. >> > >> > Oliver >> > >> > >> > Am Mi., 23. Aug. 2023 um 11:15 Uhr schrieb PJ Fanning < >> fannin...@apache.org >> > >: >> > >> > > Hi Olivier, >> > > >> > > Thanks for sharing your code. Are you planning on submitting that to >> > > TechEmpower/FrameworkBenchmarks ? >> > > >> > > On Wed, 23 Aug 2023 at 07:13, Oliver Trosien <o...@pocket-design.de> >> wrote: >> > > > >> > > > Hi, >> > > > >> > > > fair point. I have working code here (just the plain variant, not >> the one >> > > > with slick from Lightbend), >> > > > which is as you pointed out basically changing the imports plus >> doing a >> > > bit >> > > > of cleanup: >> > > > https://github.com/otrosien/FrameworkBenchmarks/pull/1/ >> > > > >> > > > Main difference to the akka version is that it runs on JDK17. Feel >> free >> > > to >> > > > use this as a baseline. >> > > > >> > > > Regards, >> > > > Oliver >> > > > >> > > > >> > > > Am Di., 22. Aug. 2023 um 19:31 Uhr schrieb PJ Fanning < >> > > fannin...@apache.org >> > > > >: >> > > > >> > > > > Thanks Olivier. We have Pekko and Pekko HTTP releases that could >> be >> > > > > benchmarked. The Akka code could probably be pretty easily forked >> and >> > > > > used to create Pekko equivalents (mainly just changing the >> imports and >> > > > > possibly some config names). >> > > > > >> > > > > I wouldn't expect there to be much difference between the Akka and >> > > > > Pekko performance numbers. >> > > > > >> > > > > If someone has time to do the initial setup, it should be fairly >> > > > > straightforward for us to maintain it going forward. >> > > > > >> > > > > For my part, I'm more interested in getting all the Pekko modules >> > > > > released and helping to get widely used Akka ecosystem libs to >> support >> > > > > Pekko too (or to create Pekko based forks). >> > > > > >> > > > > On Tue, 22 Aug 2023 at 18:10, Oliver Trosien < >> o...@pocket-design.de> >> > > wrote: >> > > > > > >> > > > > > Hi, >> > > > > > >> > > > > > I wanted to ask the project team if they want to maintain an >> > > > > implementation >> > > > > > of the framework benchmark run for pekko (you can see the akka >> > > > > > implementation here: (1)) >> > > > > > >> > > > > > I would totally understand if you'd object this kind of >> > > "Benchmarketing", >> > > > > > but it still would give the project some additional visibility. >> I do >> > > > > have a >> > > > > > local version which basically is a copy of the akka one. While >> there >> > > are >> > > > > > some framework submissions driven by individuals, they usually >> don't >> > > have >> > > > > > insights or long-term interest in maintaining these submissions >> and >> > > as a >> > > > > > result performance regressions can shed bad light on the >> project (2). >> > > > > > >> > > > > > They want to close submissions to the next round soon (3) - and >> it >> > > > > usually >> > > > > > only happens once a year, so we would need to be quick to get >> > > included. >> > > > > > WDYT? >> > > > > > >> > > > > > Regards, >> > > > > > Oliver >> > > > > > >> > > > > > (1) >> > > > > > >> > > > > >> > > >> https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/Scala/akka-http >> > > > > > (2) >> > > > > > >> > > > > >> > > >> https://github.com/TechEmpower/FrameworkBenchmarks/issues/7475#issuecomment-1607479108 >> > > > > > (3) >> > > > > > >> > > > > >> > > >> https://github.com/TechEmpower/FrameworkBenchmarks/issues/7475#issuecomment-1684087157 >> > > > > >> > > > > >> --------------------------------------------------------------------- >> > > > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> > > > > For additional commands, e-mail: dev-h...@pekko.apache.org >> > > > > >> > > > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> > > For additional commands, e-mail: dev-h...@pekko.apache.org >> > > >> > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org >> For additional commands, e-mail: dev-h...@pekko.apache.org >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pekko.apache.org For additional commands, e-mail: dev-h...@pekko.apache.org
