Parallel job rendering - Githubissues

hholzgra commented 2 years ago

Right now rendering only really works in a single threaded way, even though the underlying render library can render multiple maps at the same time.

Different ideas to run this as a system service:

re-visit / re-enable the original multi threaded implementation
run multiple service instances that simply process requests by different criteria, each of them still being single threaded; e.g having separate services for single page, multi page, and API requests)
similar to the previous item, but have a "regular" and a "slow" queue, with jobs being moved to "slow" queue after some time

hholzgra commented 2 years ago

Additional TODOs:

hholzgra commented 2 years ago

Current plan:

[x] add "queue" field to rendering job model
[x] display queue name in addition to position in list and detail view
[x] modify to_render() method to accept optional queue name
[x] add command line argument parsing to daemon.py to allow to specify queue name when calling
[x] add queue name to queue position indicator in list view
[x] file multi page layout requests to separate "multipage" queue
[x] make render status check multi-queue aware
[x] have new requests automatically filed into "default", "api" or "multipage" queue
[x] show queue name in map details
[x] allow to filter list by queue name
[ ] have default systemd service render everything regardless of queue name?

hholzgra / maposmatic