Why not using multiprocessing.Manager().dict() ?

Hello,

it would be nice if the README would describe the reason for this project. As there is already multiprocessing.Manager().dict() in the stdlib which does the same?! Is this significantly easier or faster than the multiprocessing library?

[drgarcia1986]

Hi @spaceone thanks for the comment.

We create this project to provide an alternative for distributed cache servers (like Redis) for some ephemeral data that we can share between our gunicorn/uwsgi workers across some k8s pods, but still in the experimental stage.

About multiprocessing.Manager().dict(), according to python docs:

Sharing data directly via memory can provide significant performance benefits compared to sharing data via disk or socket or other communications requiring the serialization/deserialization and copying of data.

And (IMO) multiprocessing.shared_memory it’s easier to use in our scenarios

Did you already use multiprocessing.Manager().dict() across gunicorn/uWSIG workers? I’d love to see some examples and perform some benchmarks.

[spaceone]

btw. I expected multiprocessing.Manager().dict() to be shared memory, but it seems it creates a UNIX socket and runs a server in a thread. I can’t give you any benchmarks as I don’t work with gunicorn/uWSGI.