cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6492) Have server pick query page size by default
Date Wed, 15 Jul 2015 15:16:05 GMT


Sylvain Lebresne commented on CASSANDRA-6492:

bq. However, automatically selecting the page size for non-aggregate queries is a different

How is that fundamentally different? The first reason for the page size is to make sure you
never load too much data at once and OOM the server. For both aggregate and non-aggregate
queries, that's going to depend on the size of you data in a similar way.

Don't get me wrong though: we will probably have to separate the 2 concepts at some point,
when we add {{GROUP BY}}. But let's not get ahead of ourselves. I think that as a first step,
using the data stats to pick a default page size for both kind of queries is going to be an
improvement over the status quo, and so I think we should start there.

> Have server pick query page size by default
> -------------------------------------------
>                 Key: CASSANDRA-6492
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API
>            Reporter: Jonathan Ellis
>            Assignee: Benjamin Lerer
>            Priority: Minor
> We're almost always going to do a better job picking a page size based on sstable stats,
than users will guesstimating.

This message was sent by Atlassian JIRA

View raw message