On Sun, Jan 27, 2019 at 8:03 AM Xavi Hernandez
wrote:
> On Fri, 25 Jan 2019, 08:53 Vijay Bellur
>> Thank you for the detailed update, Xavi! This looks very interesting.
>>
>> On Thu, Jan 24, 2019 at 7:50 AM Xavi Hernandez
>> wrote:
>>
>>> Hi all,
>>>
>>> I've just updated a patch [1] that imple
On Fri, 25 Jan 2019, 08:53 Vijay Bellur Thank you for the detailed update, Xavi! This looks very interesting.
>
> On Thu, Jan 24, 2019 at 7:50 AM Xavi Hernandez
> wrote:
>
>> Hi all,
>>
>> I've just updated a patch [1] that implements a new thread pool based on
>> a wait-free queue provided by us
Thank you for the detailed update, Xavi! This looks very interesting.
On Thu, Jan 24, 2019 at 7:50 AM Xavi Hernandez
wrote:
> Hi all,
>
> I've just updated a patch [1] that implements a new thread pool based on a
> wait-free queue provided by userspace-rcu library. The patch also includes
> an a
Hi all,
I've just updated a patch [1] that implements a new thread pool based on a
wait-free queue provided by userspace-rcu library. The patch also includes
an auto scaling mechanism that only keeps running the needed amount of
threads for the current workload.
This new approach has some advanta
Thanks Shyam for your inputs.
regards
Aravinda
On 08/31/2015 07:17 PM, Shyam wrote:
On 08/31/2015 03:17 AM, Aravinda wrote:
Following Changes/ideas identified to improve the Geo-replication
Performance. Please add your ideas/issues to the list
1. Entry stime and Data/Meta stime
--
On 08/31/2015 03:17 AM, Aravinda wrote:
Following Changes/ideas identified to improve the Geo-replication
Performance. Please add your ideas/issues to the list
1. Entry stime and Data/Meta stime
--
Now we use only one xattr to maintain the state of sync, called
st
Following Changes/ideas identified to improve the Geo-replication
Performance. Please add your ideas/issues to the list
1. Entry stime and Data/Meta stime
--
Now we use only one xattr to maintain the state of sync, called
stime. When a Geo-replication worker restar
