--- Comment #4 from Sean Pringle <> ---
Option A means using FORCE INDEX I guess. Since multiple indexes would increase
the overall footprint it would need testing to see if there is a net
improvement. My guess would be probably not much.

Option B sounds like application-side hash partitioning. Anything that breaks
up queries would help, though that may not speed up the api-user experience.
Along the same lines we could investigate server-side partitioning now that S1
api traffic is sent to specific slaves.

You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to