It depends whether you are using soft commits - that changes things a lot. If you aren't, then you should look in the admin interface, and see how long it takes to warm your index, and commit at least less frequently than that (commit more often, and you'll have concurrent warming searchers which will use up a lot of your memory).
If you are, then the commit frequency becomes less important. You could use soft commits between 1s and 15s, and hard commits maybe every 15s to 1min. Those seem to me to be reasonable values. Upayavira On Wed, Mar 13, 2013, at 09:19 AM, Arkadi Colson wrote: > What would be a good value for maxTime or maxDocs knowing that we insert > about 10 docs/sec? Will it be a problem that we only use maxDocs = 10000 > because it's not searchable yet... > > On 03/13/2013 10:00 AM, Upayavira wrote: > > Auto commit would seem a good idea, as you don't want your independent > > worker threads issuing overlapping commits. There's also commtWithin > > that achieves the same thing. > > > > Upayavira > > > > On Wed, Mar 13, 2013, at 08:02 AM, Arkadi Colson wrote: > >> Hi > >> > >> I'm filling our solr database with about 5mil docs. All docs are in some > >> kind of queue which are processed by 5 simultaneous workers. What is the > >> best way to do commits is such a situation? If I say to let every worker > >> do a commit after 100 docs there will be 5 commits in a short period. Or > >> should I use the autocommit option for this? > >> > >> Thx! > >> > >> Arkadi > > >
