Re: Exupery method cache

Markus Fritsche writes:

bryce@kampjes.demon.co.uk schrieb:

...

You'll need to run Exupery initializeExupery after restarting.

But doesn't that mean nil'ling the compiled methods?

Yes, but they're not yet saved with the image. They could be, but even if they were when the image starts they wouldn't be there, the startup code would need to reload the compiled code then relink it but only if the image was still running on the same architecture as it was when it was saved.

Saving compiled code is something I've thought about for a long time however it can wait until Exupery is useful for some workloads without it. i.e. provides enough of a performance gain without crashing.

Bryce