Jorey Bump wrote:
But going back to 3.2.10 hasn't restored the performance I was seeing
earlier, so this may be a nonissue. I'll report back if there are any
changes.
I tried a few more tests, cycling between versions. 3.2.10 still seems
to be a little faster, but I've been able to reach sim
Jorey Bump wrote ..
> Graham Dumpleton wrote:
>
> > There are two things you can do to gauge where any loss arises. First
> is to
> > ensure that module reloading is turned off and see how that changes things.
> >
> > PythonAutoReload Off
> >
> > The second is to reenable the old module import
Graham Dumpleton wrote:
There are two things you can do to gauge where any loss arises. First is to
ensure that module reloading is turned off and see how that changes things.
PythonAutoReload Off
The second is to reenable the old module importer as a comparison. This needs
to be done at glo
Graham Dumpleton wrote:
Jorey Bump wrote ..
I've installed it on a lightly used production server so I can test it
against some real-world apps. Initial testing indicates that it's 10-20%
slower than 3.2.10; I'm not sure why.
Can I turn on the legacy importer with a runtime configuration, or do
Jorey Bump wrote ..
> I've installed it on a lightly used production server so I can test it
> against some real-world apps. Initial testing indicates that it's 10-20%
> slower than 3.2.10; I'm not sure why.
>
> Can I turn on the legacy importer with a runtime configuration, or do I
> need to reco
