I spent a few weeks working on performance improve...
# server
c
I spent a few weeks working on performance improvements for a Kotlin server-side framework and folks here might find it interesting to look at (GitHub repo linked in the tweet) https://twitter.com/CarrotCodes/status/1541902976733876224 šŸ™‚
v
I'm always looking for a simple server side framework. Looks like this requires Java17+?
Also, hello from #edinburgh :)
@carrot unfortunately I cannot get it to compile even under JDK18. Any suggestions? There are unresolved references to
UnitDomainSocketAddress
.
c
Oh hello šŸ‘‹ Hmm thatā€™s interesting,
UnixDomainSocketAddress
should be in JDK 16?
The latest one is compiled with Java 18
@v79 I was thinking a bit more about this decided to use the newer Gradle toolchain integration, and lower the build requirement to ā€œlatest LTSā€ (Java 17) - it should pull the right JDK for you if it canā€™t find a suitable one https://github.com/CarrotCodes/Pellet/pull/67
0.0.9
is making its way to Maven Central with those changes now šŸ™‚
v
Eventually I tracked it down to a JAVA_HOME problem where it was still using Java 11. Sorted now. I was hoping to try this out on AWS Lambda but that only supports JDK11 just now. Hopefully 17 is coming soon.
I'd definitely stick to an LTS release if you can (at work we're still on Java 6 and 8...).
šŸ‘ 1
j
Interesting framework... Do yo plan to include Pellet in a public benchmark like https://www.techempower.com/benchmarks to compare with other tools?
c
Yes - an early version is already included and I'm expecting it'll show up in the round being measured now. There's a PR up to update to a build with performance improvements too šŸ˜Š