It wont obviously matter in case your columns are fat but in several cases,
(at least I could think of several cases) where you need to, for example,
just store an integer column name & empty column value. Thus 12 bytes for
the column where 8 bytes is just the overhead to store timestamps doesn't
l
I must have accidentally deleted all messages in this thread save this one.
On the face value, we are talking about saving 2 bytes per column. I
know it can add up with many columns, but relative to the size of the
column -- is it THAT significant?
I made an effort to minimize my CF footprint
I believe the timestamps *on per column basis* are only required until
the compaction time after that it may also work if the timestamp range
could be specified globally on per SST table basis. and thus the
timestamps until compaction are only required to be measure the time
from the initialization
>
> I have a patch for trunk which I just have to get time to test a bit before I
submit.
> It is for super columns and will use the super columns timestamp as the base
and only store variant encoded offsets in the underlying columns.
>
Could you please measure how much real benefit it brings
I have a patch for trunk which I just have to get time to test a bit before I
submit.
It is for super columns and will use the super columns timestamp as the base
and only store variant encoded offsets in the underlying columns.
If the timestamp equals that of the SC, it will store nothing (ju
> Using 4 bytes and 100ms resolution your can fit in 13 years of
timestamps if you use the time you deploy the cassandra DB (aka 'now')
as epoch.
In our app we will be fine with this. 100ms is good enough.
we can probably do some garbage collection on timestamps like we do on
deletes. If times
I keep thinking about the usage of cassandra timestamps and feel that for a
lot of applications swallowing a 2-4x additional cost to to memory might be
a nonstarter.
Has there been any discussion of using alternative date encodings?
Maybe 1ms resolution is too high ….. perhaps 10ms resolution? o
