Use of Threading about pickledb HOT 1 OPEN

Just read this. It's not entirely accurate, though. While Python does have a global interpreter lock (GIL), which prevents Python code from executing in more than one thread at a time, this lock is released during most calls into native code that block, including I/O (e.g., reading from or writing to disk), allowing other Python threads to run Python code. For threads that are mostly I/O bound, Python multithreading works well and the single core never needs to sit idle waiting for I/O.

It is true that the code that does the pickling/serialization prior to writing to disk can become CPU bound. Attempting to do that part after forking might be risky in a process that has multiple threads running, since the forked process will only have one thread, and any locks held by other threads at the time of fork will never be released in the forked process, which can lead to deadlocks if you are not careful.

from pickledb.