Neil Tenenholtz

For IO-bound tasks, threads are able to release the GIL enabling true parallelism. That being said, there's almost certainly a higher overhead than async code.

Have you considered leveraging a DIMSE/DICOMweb adapter (if you're able to deploy server-side)?

@chafey, (AFAIK) this would be a python client for fetching data from a serverless DICOMweb implementation (rather than specifying paths directly).

I don't have enough context on the proposal to answer your question intelligently (does it match the existing DICOMweb spec and simply leverage a different form of implementation via static...

I've only been able to attend a couple meetings thus far due to a standing conflict. That being said, if the proposal ends up being API-compatible with the existing DICOMweb...

@chafey, could you elaborate on the motivation (either here on in Monday's meeting) for not leveraging a database for metadata? I completely understand how serving of pixel data could fully...

> Databases are typically the performance and scalability choke point for medical image archives. You want to avoid them when possible and minimize them when you can't avoid them completely....

> Many PACS systems store everything they need to respond to QIDO-RS/CFIND in an RDBMS. This is problematic because the DB becomes very large and also a chokepoint for data...

The summary/descriptions found [here](https://www.dicomstandard.org/dicomweb/workflow-ups-rs/) may serve as a good starting point: * `create_work_item` * `update_work_item` * `retrive_work_item` * `cancel_work_item` * ... Alternatively, while not grammatically correct, merging "work item" into...

Resurrecting this conversation since I just ran into the same issue. I'd be happy to contribute a small PR to at least solve this for `RandomDesign`. A proposal: * Add...