You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Jeffrey (JIRA)" <ji...@apache.org> on 2015/07/01 22:39:05 UTC

[jira] [Updated] (USERGRID-752) Update Usergrid 1.0 search to use concurrent search per shard

     [ https://issues.apache.org/jira/browse/USERGRID-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey  updated USERGRID-752:
------------------------------
    Sprint: Usergrid 23, Usergrid 24  (was: Usergrid 23)

> Update Usergrid 1.0 search to use concurrent search per shard
> -------------------------------------------------------------
>
>                 Key: USERGRID-752
>                 URL: https://issues.apache.org/jira/browse/USERGRID-752
>             Project: Usergrid
>          Issue Type: Story
>            Reporter: Todd Nine
>            Assignee: Todd Nine
>
> Currently we merge all shards together with every page seek in usergrid 1.0. This means we select 20k columns, and discard 19k with each page selection.  Instead, I propose that we create an AST per shard, and execute the iterator on these shards concurrently.  We then merge on the last step, greatly reducing the amount of network I/O and discarded data on queries of large data sets.
> Proposed Changes:
> 1 AST instance per shard, evaluated concurrently via some worker pool.
> Change final gather of concurrent iterators.
> Change cursor generation to create the cursor from the merged trees.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)