sbt-native-packager
JMH
Our great sponsors
| sbt-native-packager | JMH | |
|---|---|---|
| 2 | 2 | |
| 1,514 | 738 | |
| 0.4% | 0.1% | |
| 5.8 | 2.1 | |
| 3 months ago | 9 days ago | |
| Scala | Scala | |
| BSD 2-clause "Simplified" License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sbt-native-packager
-
Why Scala is way slower than python ... and than Java too in leetcode?
As others have stated, this is mainly due to the nature of the JVM. You can try using GraalVM however, which basically complies JVM bytecode to native-code avoiding startup time issues, sbt-native-packager lets you do this quite easily.
-
SBT error when running package application: java.lang.RuntimeException: No main class detected.
IMO don't take any of this advice and use https://github.com/sbt/sbt-native-packager
JMH
-
Why is Scala so much slower than JavaScript/Node at running iterations?
Take a look at sbt-jhm for doing benchmarks. Java in particular is hard to measure because of optimizations that happen at run-time. jhm runs multiple iterations and gives tools to ensure that function calls and loops that may be optimized away are kept around and tested. You may also find some cases that are faster in node.js because the Javascript V8 engine is highly optimized.
-
Help with making backtracking more efficient
Also, if you really want to know what the performance characteristics are you should use JMH (sbt plugin https://github.com/sbt/sbt-jmh). Not sure how you are evaluating the performance but things like JVM startup and warming can make a big difference. JMH will give you a better idea of real world performance when the JVM is already started and any relevant hot code has been JIT compiled.
What are some alternatives?
sbt-assembly - Deploy über-JARs. Restart processes. (port of codahale/assembly-sbt)
JITWatch - Log analyser / visualiser for Java HotSpot JIT compiler. Inspect inlining decisions, hot methods, bytecode, and assembly. View results in the JavaFX user interface.
sbt-native-image - Plugin to generate native-image binaries with sbt
sbt-pack - A sbt plugin for creating distributable Scala packages.
honest-profiler - A sampling JVM profiler without the safepoint sample bias
sbt-jni - SBT Plugin to ease working with JNI
coursier - Pure Scala Artifact Fetching
sbt-sonatype - A sbt plugin for publishing Scala/Java projects to the Maven central.
sbt-buildinfo - I know this because build.sbt knows this.
LatencyUtils - Utilities for latency measurement and reporting
sbteclipse - Plugin for sbt to create Eclipse project definitions