|
|
|
|
|
|
by lihaoyi
572 days ago
|
|
|
All this is actually covered in the article > These benchmarks were run ad-hoc on my laptop, an M1 10-core Macbook Pro, with OpenJDK Corretto 17.0.6. The numbers would differ on different Java versions, hardware, operating systems, and filesystems. Nevertheless, the overall trend is strong enough that you should be able to reproduce the results despite variations in the benchmarking environment. > Again, to pick a somewhat easily-reproducible benchmark, we want a decently-sized module that’s relatively standalone within the project > "typical" Java code should compile at ~100,000 lines/second on a single thread > We explore the comparison between Gradle vs Mill or Maven vs Mill in more detail on their own dedicated pages |
|
|
Then answering none of my questions.
None of your "answers" you quote answers anything to me.
> Again, to pick a somewhat easily-reproducible benchmark, we want a decently-sized module that’s relatively standalone within the project
Why not take netty src? Why is a module more easily reproduceable? We chose a decently sized module because we want a decently sized module does not explain anything.
What about IO? Why lines with comments and empty lines? Or do you even? There is no mentioning in the text as far as I can see, "lines/second" implies this, but then you say "source lines per second", does this include empty lines? I think any compiler can compile a >1.000.000.000/second of empty lines in one file that is already paged into memory.