jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3916) Cor/Cow should copy in suggest dir as well if available
Date Thu, 28 Jan 2016 03:02:39 GMT

    [ https://issues.apache.org/jira/browse/OAK-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15120660#comment-15120660

Vikas Saurabh commented on OAK-3916:

[~chetanm], here's a snip of stats from my dev setup with an ootb aem instance having suggestions
enabled for {{jcr:title}}, {{jcr:description}} for {{cq:Page}} (I think most of the size in
cq:Page would be due to extracted text from resource node). I had setup suggestions for regex
prop ({{prop0}}) for aggregate lucene (that, I think, would be the worst case scenario in
terms of index-size to suggestions-size ratio)
|7276420|7.3 MB|1871|0|1871|/oak:index/cqPageLucene|64841|64.8 kB|
|66179527|66.2 MB|202136|0|202136|/oak:index/lucene|6438853|6.4 MB|

May be, we can use this as a hint to prioritize this issue.

> Cor/Cow should copy in suggest dir as well if available
> -------------------------------------------------------
>                 Key: OAK-3916
>                 URL: https://issues.apache.org/jira/browse/OAK-3916
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>            Priority: Minor
>             Fix For: 1.4
> Suggest dictionary is now stored as another OakDir under lucene indices. That means that
looking up for suggestions peeks into a lucene index which can get expensive if it requires
going to NFS/Blobstore. It'd be nice to utilize Cor/Cow for this as well.

This message was sent by Atlassian JIRA

View raw message