Re:Solving multi-core Python
by crdoconnor on Friday July 10, 2015 @01:05AM
(#9862394)
>it’s usually required that a separate Engine be used for each child process.
Yeah, provided you do this there should be no headache.
>So you have to be careful when dealing with forking and databases, which has lead us to subclass multiprocessing.Process specifically for our (common) case of wanting to continue to use the session object in the child process without having to think about recycling the Engine object.
What use case led to this being a non-negotiable requirement?
Re:Solving multi-core Python
by vosper on Monday July 13, 2015 @03:01PM
(#9880248)
It's not non-negotiable, it's for safety and convenience and DRY: We want our engineers to be able to use the database in their parallel processing jobs without having to understand the internals of SQLAlchemy, Engines, and forking.
Yeah, provided you do this there should be no headache.
>So you have to be careful when dealing with forking and databases, which has lead us to subclass multiprocessing.Process specifically for our (common) case of wanting to continue to use the session object in the child process without having to think about recycling the Engine object.
What use case led to this being a non-negotiable requirement?