02 AM Jeff Jirsa wrote:
>
> > There’s a third option which is doing bucketing by time instead of by
> hash, which tends to perform quite well if you’re using TWCS as it makes it
> quite likely that a read can be served by a single sstable
>
> > --
> > Jeff Jirsa
>
>
Folks,
I have two alternatives for the time series schema i have, and wanted to
weigh of on one of the schema .
The query is given id, & timestamp, read the metrics associated with the id
The records are inserted every 5 mins, and the number of id's = 2 million,
so at every 5mins it will be 2
ut in memory and sent back.
>
> On 21 May 2018 at 08:34, sujeet jog <sujeet@gmail.com> wrote:
>
>> Folks,
>>
>> consider a table with 100 metrics with (id , timestamp ) as key,
>> if one wants to do a selective metric read
>>
>> select m1 fro
Folks,
consider a table with 100 metrics with (id , timestamp ) as key,
if one wants to do a selective metric read
select m1 from table where id = 10 and timestamp >= '2017-01-02
:00:00:00'
and timestamp <= '2017-01-02 04:00:00'
does the read on the specific node happen first bringing all the
s we have.
>
> C*heers,
> ---
> Alain Rodriguez - @arodream - al...@thelastpickle.com
> France / Spain
>
> The Last Pickle - Apache Cassandra Consulting
> http://www.thelastpickle.com
>
> 2018-04-04 9:44 GMT+01:00 sujeet jog <sujeet@gmail.com>:
>
the datastax site has a hardware recommendation of 16CPU / 32G RAM for DSE
Enterprise, Any idea what is the minimum hardware recommendation
supported, can each node be 8CPU and the support covering it ?..
