GitHub user iyerr3 opened a pull request:

    https://github.com/apache/incubator-madlib/pull/135

    Sketch: Remove per-tuple checks

    Some of the sketch functions have checks running for each tuple in their
    aggregate. These checks include invalid transition state and invalid
    types for input data. The checks are important for the functions if run
    outside an aggregate context, but are a waste of cycles when called as
    an agg. The checks include caql calls that were estimated to eat a large
    chunk of the runtime. This work removes these checks - the average time
    saved is estimated to be around 35% for datasets ranging in size from 10
    million to 1 billion tuples.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/iyerr3/incubator-madlib 
bugfix/sketch_catalog_checks

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-madlib/pull/135.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #135
    
----
commit 617408a73ef32f25d2f8ae72ce3e9bc78cd10a4a
Author: Rahul Iyer <ri...@apache.org>
Date:   2017-05-16T22:38:08Z

    Sketch: Remove per-tuple checks
    
    Some of the sketch functions have checks running for each tuple in their
    aggregate. These checks include invalid transition state and invalid
    types for input data. The checks are important for the functions if run
    outside an aggregate context, but are a waste of cycles when called as
    an agg. The checks include caql calls that were estimated to eat a large
    chunk of the runtime. This work removes these checks - the average time
    saved is estimated to be around 35% for datasets ranging in size from 10
    million to 1 billion tuples.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to