You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, log ordering is optimized for logs arriving async as they occur. However, when the query is complete, the arrival order tends to be grouped by servers (e.g., the fastest server provides all it's logs before the next server.)
The current system for handling that is inefficient in that scenario, and we can instead load all logs and sort once. We may even want to move this server side.
Right now, log ordering is optimized for logs arriving async as they occur. However, when the query is complete, the arrival order tends to be grouped by servers (e.g., the fastest server provides all it's logs before the next server.)
The current system for handling that is inefficient in that scenario, and we can instead load all logs and sort once. We may even want to move this server side.
cc @akoshelev
The text was updated successfully, but these errors were encountered: