Compressed tree cache holds the xml data in compressed format and its d node job to do. So its obvious that for d node compressed cache should be more. Expanded tree cache is used to convert the compressed format into xml, json or some user requested format. This job is done by e node so size of this cache should be more in e node..
Thanks, Manoj Sent from my iPhone > On 19-Feb-2016, at 1:36 PM, <[email protected]> > <[email protected]> wrote: > > > Yes true, and According to Sir Jason Hunter, > > "Here are some of the key caches, what they do, and how they change in a > clustered environment: > > List Cache: > This cache holds term lists after they've been read off disk. Index > resolution only happens on D-nodes, so in a D-node group you'll probably want > to increase this size, while on an E-node you can set it to the minimum > (currently 16 Megs). > > Compressed Tree Cache: > This cache holds the XML fragments after they've been read off disk. They're > stored compressed, to reduce space and improve IO efficiency. Reading > fragments off disk > is solely a D-node task, so again you'll probably want to increase this cache > size for D-nodes and set it to the minimum for E-nodes. > > Expanded Tree Cache: > Each time a D-node sends an E-node a fragment over the wire, it sends it in > the same compressed format in which it was stored. The E-node then expands > the fragment > into a usable data structure. This cache stores the expanded tree instances. > > You'll want to raise the expanded tree cache size on E-nodes and greatly > reduce it on Dnodes. > Why not reduce it to zero? D-nodes need their own Expanded Tree Cache as a > workspace to support background reindexing. Also, if the D-node group > includes an > admin port on 8001, which is a good idea in case you need to administer the > box directly should it leave the cluster, it needs to have enough expanded > tree cache to support the > administration work. A good rule of thumb: set the Expanded Tree Cache to 128 > Megabytes on a D-node. > > When an E-node needs a fragment, it looks first in its local Expanded Tree > Cache. If it's not there, it asks the D-node to send it. The D-node looks > first in its Compressed Tree > Cache. Only if it's not there does the D-node read the fragment off disk to > send over the wire to the E-node. Notice the cache locality benefits gained > because each D-node > maintains the List Cache and Compressed Tree Cache for its particular subset > of data." > > > Regards > Abhinav > > From: [email protected] > [[email protected]] on behalf of Indrajeet Verma > [[email protected]] > Sent: Friday, February 19, 2016 1:28 PM > To: MarkLogic Developer Discussion > Subject: Re: [MarkLogic Dev General] e node and d node configuration > > Hi Vikas, > > I think, Yes. Your understanding is correct. MarkLogic provides some details > about it while giving their class room training as well. Please see below. > > > <image.png>A > > Regards, > Indy > >> On Fri, Feb 19, 2016 at 12:57 PM, <[email protected]> wrote: >> Hi , >> >> >> >> Does it recommended to have expanded tree cache more in e node and >> compressed tree cache more in d node for better performance in cluster >> environment . >> >> >> >> Regards, >> >> Vikas Singh >> >> >> >> >> >> This e-mail and any files transmitted with it are for the sole use of the >> intended recipient(s) and may contain confidential and privileged >> information. If you are not the intended recipient(s), please reply to the >> sender and destroy all copies of the original message. Any unauthorized >> review, use, disclosure, dissemination, forwarding, printing or copying of >> this email, and/or any action taken in reliance on the contents of this >> e-mail is strictly prohibited and may be unlawful. Where permitted by >> applicable law, this e-mail and other e-mail communications sent to and from >> Cognizant e-mail addresses may be monitored. >> >> _______________________________________________ >> General mailing list >> [email protected] >> Manage your subscription at: >> http://developer.marklogic.com/mailman/listinfo/general > > This e-mail and any files transmitted with it are for the sole use of the > intended recipient(s) and may contain confidential and privileged > information. If you are not the intended recipient(s), please reply to the > sender and destroy all copies of the original message. Any unauthorized > review, use, disclosure, dissemination, forwarding, printing or copying of > this email, and/or any action taken in reliance on the contents of this > e-mail is strictly prohibited and may be unlawful. Where permitted by > applicable law, this e-mail and other e-mail communications sent to and from > Cognizant e-mail addresses may be monitored. > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
