Hello! My team is trying to optimize CPU usage on a running job, and we're exploring the option of offsetting the trigger time for smoother CPU patterns. Since adjusting the window will compromise job correctness, we plan to pursue a custom trigger implementation. We were curious if the community had any thoughts or insights on this issue.

Can u share a bit more on your use case? And what impacts the CPU?

We have a job running on our cluster aggregating StatsD metrics in tumbling window, which causes CPU usage spikes due to concurrent executions. While staggering the windows using StaggerWindow that exists could help this, it will impact the job's accuracy. Instead, we want to investigate that by offsetting the trigger times without touching window start and end. we could potentially distribute the aligned windows fired executions over time to alleviate resource contention, without compromising the correctness of the computations.