Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
TL;DR
We have noticed instances in which the current latency experienced by Cloud Tasks (P99) might be high enough to affect particular workflows with high sensitivity to delays.
Summary
After a thorough investigation we determined that although this latency is negligible for the majority of use cases, particular scenarios require a way to ensure that the latency experienced by Cloud Tasks is agreed on an SLO so our customers can design their workflows accordingly and if necessary, report abnormal behaviors.
Request
We ask to define a Service Level Objective so our customers can have certainty on the latency expected by the Cloud Tasks product.
We request the possibility of custom implementation of Cloud Tasks so use cases with near real-time demands can utilize our product.