Any way to manipulate the speed entity input queues are processed?

[drdamour]

i've got some entities with very sizeable input queues that are taking days to process.

I'm on a EP3 sku in azure functions and they still are going dog slow. I've turned off everything for now cause i'm aware there's no backpressure per #2469 so i forced backpressure by turning everything off.

the actual handling code here takes nanoseconds to perform..but the waits in between whatever thunk actually processes these queued items is waaaaay too long and when it does run it's cycle it only knocks out about ~100 at a time. I gotta get through these huge queues so the entity size gets small enough to process on smaller skus. What caused these to get so big has been fixed in the code.

my control queues are all empty except the Continue event that gets posted which seems to somehow help these things along.

I don't need a long term solution just some limited scope options....does decreasing the controlQueueVisibility timeout help here?
i've tried with extendedsessios enabled and disabled it's the same results. i've got MaxEntityOperationBatchSize to 5000 but that does nothing it seems. there are only 2 entities with any entries in the queues per CustomStatus.

I'm having a tought time finding the loop/job that processes these internal queues. i see the stuff that cares about signals on control queues. I'm down for wild reflection nasty approaches if i can get it to process more of these entries for each loop or do the loops much quicker.

I'm using version 3.0.0

Updates:
we found that for a batch messages like this

digging into the ~30 items we found each invocation was taking about 6 seconds (Which seems like an eternity so we're looking into to make sure these aren't doing anything stupid....on first glance they appear to only manipulate in memory objects)

We also found

azure-functions-durable-extension/src/WebJobs.Extensions.DurableTask/Listener/TaskEntityShim.cs

Line 345 in a6e44d9

else if (stopwatch.Elapsed > TimeSpan.FromMinutes(3))

which says any given batch can only run for 3 minutes max no matter what....with no way to configure :( that seems to suck...wonder why we can't bump that to around the function timeout.