Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Liam R. E. Quin
k.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] > > > On Fr

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Bridger Dyson-Smith
gt; <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: [basex-talk] Pos

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Eliot Kimber
; | 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

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Liam R. E. Quin
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

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Eliot Kimber
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

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Tim Thompson
://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> > > > > *Fro

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Eliot Kimber
iot 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 I miss

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Eliot Kimber
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

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Eliot Kimber
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

Re: [basex-talk] Possible to Speed Up This Lookup?

2022-07-15 Thread Liam R. E. Quin
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