Message12548

Author adamburke
Recipients adamburke, filip.drozdowski
Date 2019-05-30.10:50:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559213459.89.0.5150660492.issue2776@roundup.psfhosted.org>
In-reply-to
Content
Startup times have been mentioned by a few people, and I imagine they would benefit everyone. Whether by serialization or other means, perhaps it would be worth tinkering with an API within Jython itself for externalizing the state of an interpreter? Since it seems PySystemState require a patch anyway, and juggling PySystemState, the contents of getlocals(), and so on, seems possibly brittle over time.

If you have any detailed timing traces of interpreter startup and module load times, and details of how you generated them, that would also be useful to a number of people.

One last though - PySystemState holds a number of things statically and initializes them once, which makes it a bit painful to unit test, and may also impact on this sort of thing.
History
Date User Action Args
2019-05-30 10:50:59adamburkesetmessageid: <1559213459.89.0.5150660492.issue2776@roundup.psfhosted.org>
2019-05-30 10:50:59adamburkesetrecipients: + adamburke, filip.drozdowski
2019-05-30 10:50:59adamburkelinkissue2776 messages
2019-05-30 10:50:59adamburkecreate