Open kbrock opened 3 months ago
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master
, please reply with all of the information you have about it in order to keep the issue open.
Problem
We were passing only dialog values. These
Input
values are small and did not require too much memory.After https://github.com/ManageIQ/manageiq/pull/23039, we are now passing in all
RequestTask#options
, thecontext
has ballooned in size.Proposed Solution
Input
is typically theOutput
from the previousState
inStateHistory
, so it may be as simple as droppingInput
from all records inStateHistory
.To be complete: for
Retries
(hasRetryCount
),Input
is theInput
from the previousState
. ForParallel
State
s, the previousState
inStateHistory
is not necessarily the previousState
. For the firstState
,Input
is theexecution#Input
If we deem that
Input
is easy enough to derive, or if we won't be accessing it, then dropping that should result in a record that is a little over 1/2 the size.Not sure if we can also drop
Output
for records whereInput == Output
.Dev Math
Context
Context Input
All of this data can be attributed to the
Input
:State History
Since each history record records the input and the output, this gets quite large. For errors, the
Output
will change will vary, but for test workflows, theInput
tends to be theOutput
with possibly a few values changed or added:For Envelope math: