curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cameron McKenzie <mckenzie....@gmail.com>
Subject Re: tree cache load time
Date Tue, 15 Sep 2015 23:57:35 GMT
So you could execute the all the required getChildren calls for a
particular level of the tree in a single call to ZK?

On Wed, Sep 16, 2015 at 9:54 AM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> However, there is an optimization opportunity by using ZK’s
> multi-transactions. Maybe we can explore this.
>
> -Jordan
>
>
>
> On September 15, 2015 at 6:44:46 PM, Cameron McKenzie (
> mckenzie.cam@gmail.com) wrote:
>
> It would be largely dependent upon how much data you're caching. The tree
> cache needs to recursively query ZK to populate the cache.
> cheers
>
> On Wed, Sep 16, 2015 at 9:30 AM, Vikrant Singh <
> vikrant.subscribe@gmail.com> wrote:
>
>> Hello All,
>> I am using tree cache for one of my project. Issue I am facing is with
>> the time it is taking for initialize itself. It is taking around 300ms to
>> 3-4 s to load itself.
>> This is how I am initializing the client and cache
>>
>>
>> * private val client = CuratorFrameworkFactory.newClient(hostList, new
>> ExponentialBackoffRetry(ZookeeperCache.RetryInterval.toMillis.toInt,ZookeeperCache.RetryCount))*
>>
>>
>> *val cache = TreeCache.newBuilder(client, path).build()*
>>
>>
>> post this I register for  a handler and then wait for
>> "TreeCacheEvent.Type.INITIALIZED" event.  It take on avg  300ms to 3-4 s.
>> IS there something I can do to improve this performance?
>> Thanks,
>> Vikrant
>>
>>
>>
>

Mime
View raw message