On Tue, Oct 16, 2012 at 4:13 PM, Shawn Heisey <s...@elyograg.org> wrote:
> On 10/16/2012 5:38 AM, Robert Krüger wrote:
>>
>> I use solr embedded in a desktop app and due to the consistency
>> requirements of the application I have to commit rather often. Are
>> there some best practices on how to optimize commit performance via
>> the configuration? I could easily live with slower queries or more
>> memory use as my index is rather small and queries are more than fast
>> enough for my application.
>
>
> As I understand it, the new softCommit in Solr 4.0 is designed to address
> this exact issue -- near realtime search. Basically new data is committed
> to RAM, which happens super-fast. On a longer interval, you issue a hard
> commit, which writes the data in RAM to disk.
>
> For consistency through failures, you may need to have your application keep
> track of the last document successfully hard committed. Solr 4.0 has a new
> updateLog capability that might make this unnecessary, someone with more
> experience will have to confirm or deny that.
>
> Thanks,
> Shawn
>
Great info! Thanks! I'll take a look at 4.0 then.
