This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author carljm
Recipients carljm, corona10, dino.viehland, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, shihai1991, steve.dower, tim.peters, vstinner
Date 2020-04-15.13:58:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586959092.06.0.90623757013.issue40255@roundup.psfhosted.org>
In-reply-to
Content
> Is it a common use case to load big data and then fork to use preloaded data?

A lot of the "big data" in question here is simply lots of Python module/class/code objects resulting from importing lots of Python modules.

And yes, this "pre-fork" model is extremely common for serving Python web applications; it is the way most Python web application servers work. We already have an example in this thread of another large Python web application (YouTube) that had similar needs and considered a similar approach.
History
Date User Action Args
2020-04-15 13:58:12carljmsetrecipients: + carljm, tim.peters, nascheme, gregory.p.smith, pitrou, vstinner, dino.viehland, steve.dower, corona10, pablogsal, eelizondo, shihai1991
2020-04-15 13:58:12carljmsetmessageid: <1586959092.06.0.90623757013.issue40255@roundup.psfhosted.org>
2020-04-15 13:58:12carljmlinkissue40255 messages
2020-04-15 13:58:11carljmcreate