TheOptimizationIdiot - 2:52 am on May 28, 2013 (gmt 0)
If a portion of the algo takes a large amount of processing power to generate and it's run on the front-end it might take longer to build that portion of the index, but that doesn't necessarily equate to "you should see bouncing" based on the data collected and used for "publication" of the index, because if the data is accumulated and integrated into the algo the "publication" of the index could be delayed, but if the next "publication" is not for another 7 to 10 days, then there may or may not be "bouncing" depending on what the data accumulation over the period not already accounted for is.
A shorter version is:
When something takes more processing power it could (would likely) delay "publication" of a portion of the index to some extent, but "delayed publication" is not necessarily a precursor to, or indicative of, "bouncing" in the results for any period of time. (Still hoping I'm making a bit of sense to someone besides myself LOL)