You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@flink.apache.org by Bowen Li <bo...@offerupnow.com> on 2017/09/05 06:15:22 UTC

Does RocksDB need a dedicated CPU?

Hi guys,

Does RocksDB need a dedicated CPU? Do we need to allocate one CPU for each
RocksDB while deploying Flink cluster with RocksDB state backend?

I think there's probably no need since RocksDB is a native 'library', but I
want to confirm it with Flink community.

Thanks,
Bowen

Re: Does RocksDB need a dedicated CPU?

Posted by Bowen Li <bo...@offerupnow.com>.

Thank you, Kien!

On Tue, Sep 5, 2017 at 8:01 AM, Kien Truong <du...@gmail.com> wrote:

> Hi,
>
> In my experience, RocksDB uses very little CPU, and doesn't need a
> dedicated CPU.
>
> However, it's quite disk intensive. You'd need fast, ideally dedicated
> SSDs to achieve the best performance.
>
> Regards,
>
> Kien
>
>
>
> On 9/5/2017 1:15 PM, Bowen Li wrote:
>
>> Hi guys,
>>
>> Does RocksDB need a dedicated CPU? Do we need to allocate one CPU for
>> each RocksDB while deploying Flink cluster with RocksDB state backend?
>>
>> I think there's probably no need since RocksDB is a native 'library', but
>> I want to confirm it with Flink community.
>>
>> Thanks,
>> Bowen
>>
>

Re: Does RocksDB need a dedicated CPU?

Posted by Kien Truong <du...@gmail.com>.

Hi,

In my experience, RocksDB uses very little CPU, and doesn't need a 
dedicated CPU.

However, it's quite disk intensive. You'd need fast, ideally dedicated 
SSDs to achieve the best performance.

Regards,

Kien

On 9/5/2017 1:15 PM, Bowen Li wrote:
> Hi guys,
>
> Does RocksDB need a dedicated CPU? Do we need to allocate one CPU for 
> each RocksDB while deploying Flink cluster with RocksDB state backend?
>
> I think there's probably no need since RocksDB is a native 'library', 
> but I want to confirm it with Flink community.
>
> Thanks,
> Bowen