https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42835

--- Comment #70 from Luis Bataller <[email protected]> ---
(In reply to David Cook from comment #69)
> (In reply to Luis Bataller from comment #68)
> > Regarding the numbers, here is a table with real indexing time measurements:
> > 
> > items       total(s)      gen           gen  es_wall      KB  % only items
> >        (gen+es_wall)  (total)  (only items)
> > -----  -------------  -------  ------------  -------  ------  ------------
> >     0          0.043    0.030         0.003    0.013     2.0         7.0 %
> >     1          0.075    0.065         0.032    0.010     3.7        42.7 %
> >    10          0.208    0.193         0.145    0.015    12.7        69.7 %
> >    50          0.729    0.707         0.662    0.022    51.4        90.8 %
> >   100          1.327    1.295         1.244    0.032    99.6        93.7 %
> >   250          3.434    3.393         3.297    0.041   245.2        96.0 %
> >   500          7.066    7.004         6.852    0.062   487.8        97.0 %
> >  1000         13.864   13.718        13.267    0.146  1502.4        95.7 %
> > 
> > As you can see, indexing time grows a lot with the number of items; but if
> > you
> > look closely, most of the time (over 90% from 50 items on) is spent building
> > the nested items. We are working on a solution to remove that hydration 
> > time,
> > bringing it down to the time it takes to hydrate a single item. The idea is
> > to
> > take the already hydrated document from ES and replace only the item or 
> > items
> > that have changed, so the cost of indexing a change would no longer depend 
> > on
> > how many items the record has.
> > 
> > Any comments or suggestions you may have would be much appreciated.
> 
> I don't know if "hydration" is the right term to use there, since that
> refers to rendering data on a web page with Javascript. 
> 
> When you say "[time] spent building the nested items", are you referring to
> the Perl process of building the JSON document? 
> 
> Depend on the structure of the JSON document, doing partial updates might be
> the way to go for sure.

Hi David.
Yes, the spend building time is the time Perl needs to obtain all the data
required to generate the JSON document.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list -- [email protected]
To unsubscribe send an email to [email protected]
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to