Use MockDirectoryFactory not RAMDirectoryFactory in test configs

Some of our tests don't run correctly/consistently via IntelliJ's internal JUnit runner (compared to Gradle). IntelliJ's JUnit runner is faster and better integrated, saving developer productivity. I debugged the issue. The test TestInPlaceUpdatesDistrib failed because "RAMDirectory can only be

SIP-7 New Admin UI

Hello everyone, In regards to SIP-7 and SIP-10 I would like to add my perspective and address the current concerns about imple

Re: Solr "benchmark", wikipedia

The benchmark module is focused on micro-benchmarks - benchmarking specific features or specific code. These kinds of benchmarks are notoriously difficult to get right in Java, and the benchmark module is built on JMH, in order to make it much easier to get things right. The module has a built-in

Re: Solr "benchmark", wikipedia

I've found the "benchmark" module easier to extend and write custom benchmarks with. And from what I recall it was easier to attach profilers, get flamegraphs, etc - which seems useful if there are questions around parallel-segment search. But it depends on exactly what you want. I've found solr