cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8897) Remove FileCacheService, instead pooling the buffers
Date Thu, 09 Apr 2015 09:02:14 GMT


Stefania commented on CASSANDRA-8897:

I see, so we are enforcing the page boundaries with CASSANDRA-8894 basically, but we can also
round up to the next page boundary for extra safety.

bq. FTR, we could quite easily have a bump-the-pointer shared allocator

You mean it is actually possible to implement the slicing without locks, just with an atomic
pointer? Quite possibly I guess.

Anyway, I will proceed with the implementation of the thread local pool then. What do you
mean exactly by _at the end of our complete read operation_? When the segmented file is closed
or when the read command is completed?

If we adopted increasing slab sizes how do we know when it's time to increase the size, when
there is a request which exceeds 50% of the current size, or something else?

> Remove FileCacheService, instead pooling the buffers
> ----------------------------------------------------
>                 Key: CASSANDRA-8897
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Stefania
>             Fix For: 3.0
> After CASSANDRA-8893, a RAR will be a very lightweight object and will not need caching,
so we can eliminate this cache entirely. Instead we should have a pool of buffers that are

This message was sent by Atlassian JIRA

View raw message