I guess the solution for me is to add an sql_range_step with a high value in the source definition of the delta. Hmmm maybe it would be good if TS can allow index configuration settings for main and delta.
On Monday, December 17, 2012 5:58:48 PM UTC+8, Johann Tagle wrote: > > Our setup: > > - multiple app servers, no sphinx installed. > - one dedicated server running sphinx > - TS is still used to generated the sphinx config file, then loaded to the > sphinx server > - TS will set delta=1 for new/updated records, but we let cron jobs on the > sphinx server do the full and delta index updating > > Everything is working, except I see an inefficiency with the way the delta > index is updated for one model. This model has around 5M records, with > about 10k being updated daily. Just before writing this, I ran the > statement defined by sql_query_range and saw that the values for the min > and max ids are at the opposite extremes, meaning the delta reindexing will > practically scan through the whole table when there are just 5k records > with delta=1. We indexed the delta column and so doing a simple "select * > from table where delta=1" is quite fast. > > Is there anything we can put within define_index or somewhere so that it > will generate the config for the delta source to not use ranged queries? > > Thanks > > Johann > -- You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To view this discussion on the web visit https://groups.google.com/d/msg/thinking-sphinx/-/w4FxEspJkoUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en.
