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 <[email protected]> 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: [email protected] For additional commands, e-mail: [email protected]
