Lower timeout in object processing (#17970)

On startup, the object processing pipeline would be delayed for 10ms every iteration through the loop while the end event subscriber blocked. For users with large numbers of cameras and a fair amount of detected objects, this would cause the detected objects queue length to rise and frames to be eventually dropped, leading to processing delays, incorrect frame times applied to thumbnail_data, and other seemingly unexplainable things.

frigate/record/maintainer.py

@@ -27,6 +27,7 @@ from frigate.config import FrigateConfig, RetainModeEnum
 from frigate.const import (
     CACHE_DIR,
     CACHE_SEGMENT_FORMAT,
+    FAST_QUEUE_TIMEOUT,
     INSERT_MANY_RECORDINGS,
     MAX_SEGMENT_DURATION,
     MAX_SEGMENTS_IN_CACHE,
@@ -38,8 +39,6 @@ from frigate.util.services import get_video_properties
 
 logger = logging.getLogger(__name__)
 
-QUEUE_READ_TIMEOUT = 0.00001  # seconds
-
 
 class SegmentInfo:
     def __init__(
@@ -536,7 +535,7 @@ class RecordingMaintainer(threading.Thread):
             # empty the object recordings info queue
             while True:
                 (topic, data) = self.detection_subscriber.check_for_update(
-                    timeout=QUEUE_READ_TIMEOUT
+                    timeout=FAST_QUEUE_TIMEOUT
                 )
 
                 if not topic: