Optimize out unnecessary sorts in line series visualizer

crates/viewer/re_space_view_time_series/src/line_visualizer_system.rs

@@ -1,5 +1,6 @@
 use itertools::Itertools;
 
+use re_log_types::TimeInt;
 use re_space_view::range_with_blueprint_resolved_data;
 use re_types::archetypes;
 use re_types::components::AggregationPolicy;
@@ -375,9 +376,24 @@ impl SeriesLineSystem {
                 //                This is fine, because we know there's no `TypedFallbackProvider`, but wrong if one were to be added.
                 .unwrap_or_default();
 
+            // NOTE: The chunks themselves are already sorted as best as possible (hint: overlap)
+            // by the query engine.
+            let all_chunks_sorted_and_not_overlapped =
+                all_scalar_chunks.iter().tuple_windows().all(|(lhs, rhs)| {
+                    let lhs_time_max = lhs
+                        .timelines()
+                        .get(&query.timeline())
+                        .map_or(TimeInt::MAX, |time_column| time_column.time_range().max());
+                    let rhs_time_min = rhs
+                        .timelines()
+                        .get(&query.timeline())
+                        .map_or(TimeInt::MIN, |time_column| time_column.time_range().min());
+                    lhs_time_max <= rhs_time_min
+                });
+
             // This is _almost_ sorted already: all the individual chunks are sorted, but we still
             // have to deal with overlap chunks.
-            {
+            if !all_chunks_sorted_and_not_overlapped {
                 re_tracing::profile_scope!("sort");
                 points.sort_by_key(|p| p.time);
             }