#698: profile bibknowledge.get_kbd_values_for_bibedit
---------------------------+----------------------
Reporter: cdickins | Owner: cdickins
Type: task | Status: new
Priority: minor | Milestone: v1.0
Component: BibKnowledge | Version:
Resolution: | Keywords:
---------------------------+----------------------
Comment (by jblayloc):
In the bibknowledge module there's an inline comment indicating that the
overhead should only be 5 to 10% of the call time (versus a regular
dynamic KB). I too have often wondered why it seemed like a good idea to
build it this way. I'm not sure, but I think it was done this way to
optimize the speed of working on bibedit - from bibedit.js or whatever you
can specify essentially arbitrary searches to be used as autocompletes.
Crystalizing into a regular dynamic KB seems a lot better to me from the
standpoint of increasing formality.
It's probably not necessary for a backend tool like BibEdit, but if we
wanted to go for better performance we'd probably want to have a cron job
do the searches for us and generate a regular KBR, which I think is the
fastest thing bibknowledge knows about.
--
Ticket URL: <http://invenio-software.org/ticket/698#comment:1>
Invenio <http://invenio-software.org>
