lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Bernstein (JIRA)" <>
Subject [jira] [Resolved] (SOLR-9905) Add NullStream to isolate the performance of the ExportWriter
Date Fri, 30 Dec 2016 20:35:58 GMT


Joel Bernstein resolved SOLR-9905.
    Resolution: Resolved

> Add NullStream to isolate the performance of the ExportWriter
> -------------------------------------------------------------
>                 Key: SOLR-9905
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Joel Bernstein
>         Attachments: SOLR-9905.patch
> The NullStream is a utility function to test the raw performance of the ExportWriter.
This is a nice utility to have to diagnose bottlenecks in streaming MapReduce operations.
The NullStream will allow developers to test the performance of the shuffling (Sorting, Partitioning,
Exporting) in isolation from the reduce operation (Rollup, Join, Group, etc..). 
> The NullStream simply iterates it's internal stream and eats the tuples. It returns a
single Tuple from each worker with the number of Tuples processed. The idea is to iterate
the stream without additional overhead so the performance of the underlying stream can be
> Sample syntax:
> {code}
> parallel(collection2, workers=7, sort="nullCount desc", 
>       null(search(collection1, 
>                    q=*:*, 
>                    fl="id", 
>                    sort="id desc", 
>                    qt="/export", 
>                    wt="javabin", 
>                    partitionKeys=id)))
> {code}
> In the example above the NullStream is sent to 7 workers. Each worker will iterate the
search() expression and the NullStream will eat the tuples so the raw performance of the search()
can be understood.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message