Bug 1606276 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Small cleanup that can happen, might also reduce load time for cache loads.

Right now if we load spocs data from fresh or cache, we then filter blocked stories and remove frequency capped spocs from those results.

If we instead, updated spocs cache as stories got blocked/seen we wouldn't need to do it again from cached loads as it would already be up to date. We would only need to update fresh spocs.

This doesn't apply to feeds, this has a slightly more complex handling because it's got placements, frequency capping, and flight id migration, so the code paths are separate and different currently.
Small cleanup that can happen, might also reduce load time for cache loads.

Right now if we load spocs data from fresh or cache, we then filter blocked stories and remove frequency capped spocs from those results.

If we instead, updated spocs cache as stories got blocked/seen we wouldn't need to do it again from cached loads as it would already be up to date. We would only need to update fresh spocs.

This doesn't apply to feeds, this has a slightly more complex handling because it's got placements, frequency capping, and flight id migration, so the code paths are separate and different currently. See bug 1606277

Back to Bug 1606276 Comment 0