On 17.8.2016 13:21, David Kupka wrote:
On 08/08/16 13:26, Jan Cholasta wrote:
On 4.8.2016 16:32, David Kupka wrote:
On 03/08/16 16:33, Jan Cholasta wrote:
On 3.8.2016 16:23, David Kupka wrote:
On 21/07/16 10:12, Jan Cholasta wrote:
On 20.7.2016 14:32, David Kupka wrote:
On 15/07/16 12:53, David Kupka wrote:
After Honza introduced thin client that builds plugins and commands
dynamically from schema client became much slower. This is only
instead of importing a module client now must fetch the schema from
server, parse it and instantiate the commands using the data.
First step to speed it up was addition of schema cache to client.
removed the RTT and download time of fetching schema every time.
Now the most time consuming task became displaying help for
topics and command and displaying individual topics. This is simply
because of the need to instantiate all the commands to find the
relations between topics and commands.
All the necessary bits for server commands and topics are
schema cache so we can skip this part and generate help from it,
Not so fast!
There are client plugins with commands and topics. So we can
basic bits (list of all topics, list of all commands, list of
for each topic) from schema and store it in cache. Then we need
through all client plugins and get similar bits for client plugins.
we can merge and print.
Still the client response is not as fast as before and I this it
can't be. Also first time you display particular topic or list
longer because it must be freshly generated and stored in cache for
use. And this is what the attached patches do.
Reimplemented so there is no need to distinguish client plugins and
The main idea of this approach is to avoid creating instances of the
commands just to get the information about topic, name and summary
needed for displaying help. Instead class properties are used to
the information directly in schema.
I think this would better be done in Schema.read_namespace_member,
because Schema is where all the state is.
(BTW does _SchemaNameSpace.__getitem__ raise KeyError for
keys? It looks like it doesn't.)
How about setting _schema_cached to False in Schema.__init__() rather
that getattr()-ing it in _ensure_cached()?
ClientCommand.doc should be a class property as well, otherwise
won't work on it correctly.
_SchemaCommand.doc should not be a property, as it's not needed for
.summary to work on it correctly.
Otherwise works fine for me.
Updated patches attached.
Pushed to master: 229e2a1ed9ea9877cb5e879fadd99f9040f77c96
I've made and reviewer overlooked some errors. Attached patches fix
Shame on me.
1) When schema() raises SchemaUpToDate, the current code explodes:
ipa: ERROR: KeyError: 'fingerprint'
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/ipalib/cli.py", line 1348, in
File "/usr/lib/python2.7/site-packages/ipalib/plugable.py", line 707,
File "/usr/lib/python2.7/site-packages/ipalib/plugable.py", line 422,
File "/usr/lib/python2.7/site-packages/ipalib/plugable.py", line 585,
for package in self.packages:
File "/usr/lib/python2.7/site-packages/ipalib/__init__.py", line 919,
line 92, in get_package
plugins = schema.get_package(api, server_info, client)
line 558, in get_package
fingerprint = str(schema['fingerprint'])
line 483, in __getitem__
2) We read server info every time get_package() is called. It should be
cache similarly to how the schema is cached in the api object.
3) Some of the commands are still fully initialized during "ipa help
Updated patches attached.
Pushed to master: 6e6cbda036559e741ead0ab5ba18b0be0b41621e
Manage your subscription for the Freeipa-devel mailing list:
Contribute to FreeIPA: http://www.freeipa.org/page/Contribute/Code