lucene-grep

The JVM is a master of gradually closing the gap. Over the last decade: - Garbage collectors have required far less tuning; with G1, Shenandoah, ZGC it's likely that your application will need little tuning on normal sized heaps. - modules, jlink etc allow one to build a much smaller Java application by including only those parts of the JVM that one needs. - Graal native images are real. These boast a far lower startup overhead and much lower steady state memory usage for simpler applications. Probably my counterexample of choice is this: https://github.com/dainiusjocas/lucene-grep - it uses Lucene, one of the best search libraries (core of Elasticsearch, Solr, most websites), which is notoriously not simple code, to implement grep-like functionality. In simple cases, they demonstrate a 30ms whole process runtime with no more than 32MB of

Opened an issue and asked this: https://github.com/dainiusjocas/lucene-grep/issues/99

Here goes: https://github.com/dainiusjocas/lucene-grep/issues/84 I realize some relatively obscure Finnish stemmer and Lucene with GraalVM aren't exactly a common use case. I did some testing and provided my use case. I certainly have much English language content to search with using lucene-grep. So, thank you for making it!

Author of lmgrep here. Could you create an issue for Finnish text analysis? https://github.com/dainiusjocas/lucene-grep/issues I'd take look.

Very nice, examples are in the repository https://github.com/dainiusjocas/lucene-grep#text-analysis

Yes, it is there as an in-text link: "Then the most complicated part was to prepare executable binaries for different operating systems. Plenty of CPU, RAM, VirtualBox with Windows and macOS virtual machines, and here we go." https://github.com/dainiusjocas/lucene-grep/releases/tag/v20...