Hi, *The Scenario: *We *atomically* update (*no deletion*) data for our Auto-Suggest index every morning on master. The slave is our production server. Master replicates to slave when the traffic is least on production server.
*Objective: *Faster search. Real-Time updates are really not necessary. *Query: *I was reading articles about optimizations, merging and committing. My basic queries can be summed up as: 1. Should we optimize the index after atomic updates before replication? This equates to single optimization operation daily during low traffic (morning). 2. Since speed is our focus (and not storage resource at this time) and that optimizations builds the index again by merging, does this mean that the whole cache is also refreshed? If yes, this would mean that we would be flushing cache everyday and if we really want to go ahead with this, I think, we should relook about autowarming. 3. What's tradeoff in our scenario? Storage v/s Speed? Or am I missing something. What if I choose not to optimize? -- -- Regards, *Paras Lehana* [65871] Software Programmer, Auto-Suggest, IndiaMART Intermesh Ltd. 8th Floor, Tower A, Advant-Navis Business Park, Sector 142, Noida, UP, IN - 201303 Mob.: +91-9560911996 Work: 01203916600 | Extn: *8173* -- IMPORTANT: NEVER share your IndiaMART OTP/ Password with anyone.
