Memory Limit in Fusion Scenario Monitor

[#1]

I am a power user/resource hog in Fusion. I perform 10s of thousands of operations and frequently need to move around 100s of MBs if files. As such, I run out of your paltry 1GB of memory frequently. I am informed by Support that there is no way to monitor the current memory usage while running a Fusion scenario. And the official answer is "just do less".

I argue this is a PRIME case for providing us access to poll the current used memory from within a running scenario. Similar to an Environment variable. This way I would not have to run hard until I hit a brick wall, I could periodically poll the current memory usage and decide if I need to gracefully stop or if I am able to continue on.

I am surprised that this doesn't already exist, as it is rather asinine that I can "do anything" in Fusion, but run it hard until it breaks in a non-graceful way.

Thank you,

Wes-

(Very large, multi-milion dollar client)

[#2]

Hello wes,

This is a very unsatisfactory answer from Adobe Support!

Perhaps it can make sense to have a look on the company, which provides the technology for Fusion.
https://www.make.com/en/pricing

They do not have any Workfront modules, as they are Adobe exclusive, but you will be able to do anything Workfront related also there by using custom API modules. Besides that, they offer some quite interesting features, like being able to create your own apps and modules...

Regards

Lars

[#3]

Hello Wes,

Have you found any working solution for low memory issue? If so, what is it?

Could you please advise?

Thank you!

[#4]

Hello Viktoriia,

No, Adobe has not given us access to any system variables yet. So, you just have to use your best judgement in not allowing more than 1GB worth of data to flow through a Fusion Scenario.

If you break the limit, the scenario just stops... quite ungracefully.

Wes-

[#5]

That's what started happening with one of our large scenarios recently. Although, it was running successfully before, now it started running out of memory and stopping.

How do you achieve this data management? Are you splitting it into batches before feeding to the scenario?

[#6]

Hello Viktoriia,

It really depends on what you are doing, but generally... if it's repetition that is killing you because you are repeating an action over and over. Try limiting the iterations down to smaller "chunks" and call the scenarios a few times, instead of one.

Or you can try breaking out big loops and sending each iteration to a focused scenario for processing via a web hook.

Those are a few ideas I can give you without knowing exactly what you are doing.

Wes-

[#7]

Thank you, Wes! It started failing on a numeric aggregator that is counting items meeting certain condition and only when the number is high.

I may try to split this part of the scenario into a separate one, but would prefer not to at this point, if there are some other options available.