cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kibirev (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4681) SlabAllocator spends a lot of time in Thread.yield
Date Tue, 18 Sep 2012 21:17:07 GMT


Oleg Kibirev commented on CASSANDRA-4681:

The benchmark exercised two column families. I think the key is that I am using a large number
of very small column names/values and insert concurrently from dozens of threads (due to characteristics
of the real world use case). The system used has 24 CPU cores and an SSD raid. So basically
there is a very high rate of allocations and large number of concurrent threads hitting the
same SlabAllocator. 
> SlabAllocator spends a lot of time in Thread.yield
> --------------------------------------------------
>                 Key: CASSANDRA-4681
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.5
>         Environment: OEL Linux
>            Reporter: Oleg Kibirev
>         Attachments:
> When profiling high volume inserts into Cassandra running on a host with fast SSD and
CPU, Thread.yield() invoked by SlabAllocator appeared as the top item in CPU samples. The
fix is to return a regular byte buffer if current slab is being initialized by another thread.
So instead of:
>                if (oldOffset == UNINITIALIZED)
>                 {
>                     // The region doesn't have its data allocated yet.
>                     // Since we found this in currentRegion, we know that whoever
>                     // CAS-ed it there is allocating it right now. So spin-loop
>                     // shouldn't spin long!
>                     Thread.yield();
>                     continue;
>                 }
> do:
> if (oldOffset == UNINITIALIZED)
>     return ByteBuffer.allocate(size);
> I achieved 4x speed up in my (admittedly specialized) benchmark by using an optimized
version of SlabAllocator attached. Since this code is in the critical path, even doing excessive
atomic instructions or allocating unneeded extra ByteBuffer instances has a measurable effect
on performance

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message