Forge’s Async Compute Model Needs More Transparency

Forge Forge Modules and Product Triggers
, ,
1

Last week Atlassian quietly rolled out Async Compute usage metrics inside the Forge developer console. However, what they didn’t disclose is: how is this calculation derived, as it seems completely off from your typical GB-seconds calculation. There’s no further information about it other than what they posted on https://developer.atlassian.com/changelog/#CHANGE-3120

What exactly differentiates async compute from sync compute?

Is async compute counted when:

  1. A Forge module like scheduledTrigger, async events, or queues invokes a function?

OR

  1. Any function execution that happens outside a user request lifecycle?

It would help the ecosystem if Atlassian clarified:

  1. Exactly what events count as async compute

  2. Whether queue pipelines multiply compute usage

  3. How developers should estimate async workloads

  4. Whether background compute should be priced differently

If the Forge team could clarify the above, that would be helpful so using the background modules can be a little bit predictable as we build on Forge.

2 Likes
2

Seems related to this discussion: Questions about billing for Forge asynchronous invocations, perhaps good to also chime in there!

3

Thank you. I’ll comment there.