The multiprocessing library's Pool is used for the reports' parallel processing. This by default shouldn't cause an issue, but unfortunately there are some runtime environments, such as AWS Lambda, where /dev/shm (shared memory for processes) doesn't exist.
To address the above, it would be beneficial to change the multiprocessing.Pool implementation to use Pipe + Process instead, so that the multi-core/multi-process handling is more widely supported.
The multiprocessing library's Pool is used for the reports' parallel processing. This by default shouldn't cause an issue, but unfortunately there are some runtime environments, such as AWS Lambda, where
/dev/shm(shared memory for processes) doesn't exist.To address the above, it would be beneficial to change the multiprocessing.Pool implementation to use Pipe + Process instead, so that the multi-core/multi-process handling is more widely supported.
I am happy to work on an implementation.