Dear FME Enthusiasts,
I'd like to draw attention to a current limitation within FME regarding job statistics on Flow Streams. Unlike other FME processes, the Flow Stream lacks the capability to provide detailed job statistics due to its reliance solely on translation completion. While other FME processes exhibit CPU usage metrics, the Stream does not offer this visibility.
Introducing job statistics for Flow Streams would immensely benefit the community. With access to CPU usage data specific to Stream processes, users would be empowered to optimize their workspaces, potentially reducing CPU load. Moreover, this enhancement would enable better monitoring of resource utilization.
In our company, we've observed that a running Stream consumes approximately 4-5 seconds per hour. However, despite this resource consumption, monitoring tools such as the database and job history reflect zero usage, even after the Stream has terminated.
Effective management of CPU resources is critical, especially for Streams, to avoid excessive CPU hours on Dynamic Engines. Providing insights into CPU usage for Streams would aid in this endeavor.
I encourage the consideration of this enhancement to improve the monitoring capabilities within FME, benefiting users across various workflows.
Reference: FMEFLOW-21844.
