Niels Erik
Dabbler
- Joined
- Aug 9, 2015
- Messages
- 18
Hi
I have run into a Github all the way down problem..
Iocage is slow at starting on my system (CPU Intel(R) Atom(TM) CPU C2750 @ 2.40GHz), even the splash screen takes 4 sec to display..
All commands takes 3-4 sec. to execute no matter what..
I have done some investigation, and IOcage uses 2-3 secs loading the python module 'requests' used to download new jail templates.(kind of wget functionality)
The requests module again imports several crypto modules, and import cryptography.x509 seem to be the main culprit.
I have raised an issue on iocage https://github.com/iocage/iocage/issues/517 , but they point the finger at requests and would like to close the issue as an upstream problem. See https://github.com/requests/requests/issues/4278, and https://github.com/requests/requests/issues/4315.
Requests point at the optional imports. (e.g. x509, in my case it is a part of the FN11.1 distribution), and might look into it in the future..
I assume the the slow load of requests/x509 are a non issue in most applications.
The problem is that Iocage is an interactive program, and every command line take 3-4 sec. to execute.
And it is only 1 out of 1000 command line invocations where i actually need requests to download an new template.
Who should fix this ?
-FreeNAS could remove some crypto libs from their distribution.. (Not a good idea..)
-Iocage could implement lazy import some some rarely used libs..
-Requests could implement lazy import until the API functions are invoked..
-crypto libs could try to optimize their software..
Versions
FreeNAS 11.1 U4
Python 3.6
Iocage Version 1.0 ALPHA
requests-2.18.1-py3.6.egg-info
I have run into a Github all the way down problem..
Iocage is slow at starting on my system (CPU Intel(R) Atom(TM) CPU C2750 @ 2.40GHz), even the splash screen takes 4 sec to display..
All commands takes 3-4 sec. to execute no matter what..
I have done some investigation, and IOcage uses 2-3 secs loading the python module 'requests' used to download new jail templates.(kind of wget functionality)
The requests module again imports several crypto modules, and import cryptography.x509 seem to be the main culprit.
I have raised an issue on iocage https://github.com/iocage/iocage/issues/517 , but they point the finger at requests and would like to close the issue as an upstream problem. See https://github.com/requests/requests/issues/4278, and https://github.com/requests/requests/issues/4315.
Requests point at the optional imports. (e.g. x509, in my case it is a part of the FN11.1 distribution), and might look into it in the future..
I assume the the slow load of requests/x509 are a non issue in most applications.
The problem is that Iocage is an interactive program, and every command line take 3-4 sec. to execute.
And it is only 1 out of 1000 command line invocations where i actually need requests to download an new template.
Who should fix this ?
-FreeNAS could remove some crypto libs from their distribution.. (Not a good idea..)
-Iocage could implement lazy import some some rarely used libs..
-Requests could implement lazy import until the API functions are invoked..
-crypto libs could try to optimize their software..
Versions
FreeNAS 11.1 U4
Python 3.6
Iocage Version 1.0 ALPHA
requests-2.18.1-py3.6.egg-info
