Hi Paul Sphinx paginates over document records when indexing, instead of grabbing everything all at once (you'll notice the $start and $end placeholders in the generated queries). You'll want to change the sql_range_step value to grab much larger windows of records (perhaps 1,000,000,000):
http://pat.github.io/thinking-sphinx/common_issues.html#slow_indexing Cheers -- Pat On 09/05/2013, at 11:49 PM, Paul Bellamy wrote: > Hi, > > It seems that when the range between IDs is too large the indexer will just > hang. For example: > > We have two documents, with ids 1, and 999,999,999. The indexer begins > sending many queries to the database (Postgres), which contain where clauses > similar to: ... WHERE ("documents"."id" >= 11331585 AND "documents"."id" <= > 11332608 AND documents.deleted_at IS NULL) ... > > We are on Sphinx 2.0.4-release (r3135). > > Any suggestions? Why does sphinx paginate based on ID, not by using a LIMIT > clause? > > Thanks for the help, > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Thinking Sphinx" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/thinking-sphinx?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/thinking-sphinx?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
