I was troubleshooting some very slow circup sessions (that I think turned out to be a local system issue) but in going down that rabbit hole I developed with Claude's help a version of WebWorkflow that honors KeepAllive. circup takes advantage of keep alive but my measurements show little to no performance improvement to be had there for circup.
So the question for discussion is whether or not anyone has thought of enabling KeepAlive (persistent connections) in WebWorkflow and whether there is interest in me posting the PR for people to bang on or should we leave things as they are.
My implementation currently times out after 2s so only a running connections is kept alive.
The changed behavior is one connection could hold until it finished rather than the current interleaving of single requests where a web connection and circup can work concurrently.
I can't say I've tested all cases by any means but I've run for a few hours with the Keep Alive code and circup runs the same as usual and the filesystem operations in Web Workflow work fine. So far nothing I've tried seems to have regressed.
I was troubleshooting some very slow circup sessions (that I think turned out to be a local system issue) but in going down that rabbit hole I developed with Claude's help a version of WebWorkflow that honors KeepAllive. circup takes advantage of keep alive but my measurements show little to no performance improvement to be had there for circup.
So the question for discussion is whether or not anyone has thought of enabling KeepAlive (persistent connections) in WebWorkflow and whether there is interest in me posting the PR for people to bang on or should we leave things as they are.
My implementation currently times out after 2s so only a running connections is kept alive.
The changed behavior is one connection could hold until it finished rather than the current interleaving of single requests where a web connection and circup can work concurrently.
I can't say I've tested all cases by any means but I've run for a few hours with the Keep Alive code and circup runs the same as usual and the filesystem operations in Web Workflow work fine. So far nothing I've tried seems to have regressed.