> Nah, optimization is tricksy.
True. Both for the optimizer and the developer. I can spot two indicators for …
> db:open($rkDatabase)/doc-where-used-index/where-used-entry/@key[xs:integer(.)
> eq 9151416]
… not being rewritten for index access:
• If $rkDatabase is not static, it won’t be poss
cebook.com/servicenow>
>
> From: BaseX-Talk on
> behalf of Liam R. E. Quin
> Date: Friday, July 15, 2022 at 4:55 PM
> To:
> basex-talk@mailman.uni-konstanz.de >
> Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
> [External Email]
>
>
>
t; | Facebook
> <https://www.facebook.com/servicenow>
>
>
>
> *From: *BaseX-Talk on behalf
> of Liam R. E. Quin
> *Date: *Friday, July 15, 2022 at 4:55 PM
> *To: *basex-talk@mailman.uni-konstanz.de <
> basex-talk@mailman.uni-konstanz.de>
> *Subject: *Re: [
; |
YouTube<https://www.youtube.com/user/servicenowinc> |
Facebook<https://www.facebook.com/servicenow>
From: BaseX-Talk on behalf of Liam
R. E. Quin
Date: Friday, July 15, 2022 at 4:55 PM
To: basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
[Ext
On Fri, 2022-07-15 at 21:20 +, Eliot Kimber wrote:
>
> return (db:option('attrindex'),
> for $node in $map
> return prof:track(db:open($rkDatabase)/doc-where-used-
> index/where-used-entry/@key[xs:integer(.) eq 9151416])?time !
> util:formatTime(.)
can you take the db:open() call
x-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
[External Email]
Is there a performance difference when using db:attribute() instead[1]?
Tim
[1]
https://docs.basex.org/wiki/Database_Module#db:attribute<https://urldefense.com/v3/__https:/docs.basex.org/wi
<https://www.servicenow.com>
>
> LinkedIn <https://www.linkedin.com/company/servicenow> | Twitter
> <https://twitter.com/servicenow> | YouTube
> <https://www.youtube.com/user/servicenowinc> | Facebook
> <https://www.facebook.com/servicenow>
>
>
>
From: Eliot Kimber
Date: Friday, July 15, 2022 at 3:39 PM
To: Liam R. E. Quin , basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
Yes, turning on the attribute index definitely improves performa nce
dramatically, which is no surprise. Not sure how
om: Eliot Kimber
Date: Friday, July 15, 2022 at 3:01 PM
To: Liam R. E. Quin , basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
There are on the order of 50K index entry items.
I think the attribute index is probably the answer—for some reason I ass
om/user/servicenowinc> |
Facebook<https://www.facebook.com/servicenow>
From: Liam R. E. Quin
Date: Friday, July 15, 2022 at 1:22 PM
To: Eliot Kimber ,
basex-talk@mailman.uni-konstanz.de
Subject: Re: [basex-talk] Possible to Speed Up This Lookup?
[External Email]
On Fri, 2022-07-15 at 1
On Fri, 2022-07-15 at 18:04 +, Eliot Kimber wrote:
> collection($rkDatabase)/doc-where-used-index/where-used-
> entry[string(@key) eq string(db:node-id($node))]
>
> Where the markup is shown in [1] below.
>
> Using prof:track() I’m measuring a consistent 0.036 seconds per
> lookup,
could it
I generate a “where used” index as an XML doc in a separate database.
I’m then doing lookups against this index like this where $node is the element
I want to find the index entry for:
collection($rkDatabase)/doc-where-used-index/where-used-entry[string(@key)
eq string(db:node-id($node))]
12 matches
Mail list logo