> > Regardless of the server you choose, please be aware they may (though I am > pretty sure they all will) all cause issues with your current codebase due > to the characteristics of copy-on-write memory optimization. Usually the > issues I've seen are with database connections and random seed generators. > Most of the libraries you are probably using will support correcting this > with specific calls to make after the process forks. If you're using > SqlAlchemy, look at Engine.dispose() and most crypto libraries have an > `atfork` function. >
Thank you Jonathan. This is golden, rarely seen, insight. Br, Mikko -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAK8RCUsLPsfw7AMzf2T5GJUrt6BdTeo9FW9Tyf0g46XCLES%3DKg%40mail.gmail.com.
