Robert Sachunsky

> What we do need here is an API that allows getting a (polygon-masked, via alpha channels and/or bg fill) segment image via the same ad-hoc creation or AlternativeImage retrieval...

And here's a recipe for doing workspace parallelization with the new workflow server and GNU parallel: N=4 for ((i=0;i

> Please note that (as already explained [here](https://gist.github.com/bertsky/9cd1a6ed9c2f3925a5339ed52f9be458#gistcomment-3544628)) this only inreases efficiency for Python processors in the current venv, so bashlib processors or sub-venv processors will still be run via...

b4a8bcb0: Gosh, I managed to forget that one essential, distinctive change: triggering the actual instantiation! (Must have slipped through somewhere on the way from [the proof-of-concept standalone](https://gist.github.com/bertsky/9cd1a6ed9c2f3925a5339ed52f9be458) to this integrated...

I wonder if Flask (especially its server component, branded as `development` and has a `debug` option) is efficient enough. IIUC we actually need multi-threading in the server if we also...

Another edge for performance might be transferring the **workspace** to fast storage during processing, like a **RAM disk**. So whenever a `/process` request arrives, clone the workspace to `/tmp`, run...

@kba, note ccb369a is necessary for core in general since resmgr wants to be able to identify the startup CWD from the workspace. The other two recent commits add proper...

> I think I'll incorporate uwsgi (which does preforking) to achieve workspace parallelism. The server will have to do `parse_tasks` and `instantiate` in a dedicated function with Flask's decorator `@app.before_first_request`...

Updated help text for `ocrd workflow server` now reads: ``` Usage: ocrd workflow server [OPTIONS] TASKS... Start server for a series of tasks to run processor CLIs or APIs on...

> I just confirmed this by testing: If I start a workflow with multiple TF processors, the last one will steal the others' session. You have to explicitly create sessions,...