ÃÛ¶¹ÊÓƵ

Transcript

Hello, everyone. Thanks for joining. Us. We’ll give a couple of minutes for everybody to join, and then we. Can get started.

Okay. It’s just a couple of minutes past 11 to let me. Just get started. And let. Me. Yeah. So let me share my screen.

Okay. I’ll be able to see my screen. Hello, everybody. Yep. Thanks, Katie. Hello, everyone. Thanks for joining us for today’s session. Today’s topic for the webinar is Optimizing and Performance. And, Caching strategies and techniques. This basically about how we can optimize a performance by using better caching. And then what are the different techniques for. Managing, Better caching. So let me go to the next.

Okay. Here is the agenda, that we have for the current, the session. We will have a brief introduction for myself and then the co-host, my colleague, and then we talk about a brief. Overview of, Caching and then what are the, different caching mechanisms and different tiers of caching. And we have a quick, look at what are the, What is the demo that we can have, with respect to caching on the dispatcher side? Majorly. And then, a couple of use cases. Of, Managing caching on the CDM, which I’ve seen with multiple customers. So, we look at two different use cases which are commonly used across M cloud to with this, which could lead to a m cloud service.

And the same thing, works similarly on the Ms. to the customer as CM. And we look at the demo of what are the different. Caching. Attributes to caching configuration on the CDM that we can do on the, dispatcher.

And we also talk about, the fragment caching.

But. How we handle the dynamic content on a page and then how we make sure dynamic content is not caching the rest of the cache so that the overall page performance can be improved. And we have a we’ll have a quick demo on that. And then we will talk about. Different techniques to debug any caching issue, be at the browser level dispatcher or CDF and followed by. Q&A.

Okay, so coming to the introduction, myself, Senior field is needed in field engineering team at ÃÛ¶¹ÊÓƵ. I’ve been working with ÃÛ¶¹ÊÓƵ since 210, 20, 21. And then. I’m based out of East Coast Atlanta.

Yeah. And if you want to give a brief introduction about. Yes. Okay. Sure. Thanks, Bo. And hi, everyone. My name is Anniston, and I’m also, in the same team as Bo. I’m one of the senior field engineer at ÃÛ¶¹ÊÓƵ. I am based out in San Jose, and I come with more than 12 years of experience on Am. Thank you. Okay. Thanks, Anish. Okay. So we’ll we’ll quickly look at the overview of what is, caching. In a cloud service or in general in a, in black form based on prem, Amazon cloud service.

So e. Caching is basically. Storing the. Resources which are coming from. A, Which are accessed by the end user, the, the browser and storing them at a different layers. Of the platform. It can be. User browser, it can be a dispatcher, to create. So, so. Why why we need caching. So caching basically enhances the overall page performance. If we have a better caching at, different layers of, caching, the request to the end user can be served quickly with assets or pages, or B can be any resource. On the page. And Utilizing multiple layers of caching, increases the overall page load. And then Thereby, it. It looks lot fat, lot faster. For the B, end user and then significantly enhancing the overall user experience for the end user.

Page and site performance directly impact SEO because. Of, page speed. Is one of the key factor within SEO. So, Having the better page performance page load performance gives a better SEO rating. And in. This, Webinar will look at various caching strategies and the best practices around. M, performance improvement.

So if we look at, in general architectures. Will be a browser and then published year and then out the year.

So this particular diagram. Is. Much related to. Cloud service where CDM dispatch and publish instance are managed as a single tier, which is published here.

But in general, it can be this, it can be the same. I mean, it will. Have a similar, kind of architecture for the, the setup as well. Like Ms…

End user tries to access the page from the browser. Request goes to CDM. If. And CDM dispatcher and then the publish, depending on whether a request can be served from either CD and or dispatcher, the train fine. Otherwise request will go to the origin server which is published, and then page will be rendered and then returned to the, And use it. Okay. So if we look at layers of caching, there are majorly three layers of caching in a in a conventional. Picture. Like if we look at a, cloud service majorly. So these three are involved. Where. Caching at the browser. So browser can cache the content. You can set. Cache control headers to control how much, how much time the cache of a particular resource needs to be present and, managed and maintained in the, browser cache before it gets invalidated. And then, the cache control headers and then expose headers are, couple of approaches with which we can manage how much time a resource can, exist on browser cache. It.

And then the second one is the. The CD layer. Where you. Can cache content at the edge and, cache control header and then surrogate control header, which is specific to fastly on the IBM Cloud Service. These two. Are. Used to manage how long a resource resides on a client cache before it even gets, revalidated. Or invalidated on the, client.

And then. The third layer of caching is on the dispatcher. You can define, cache tool under the form based on the rules you can define what hierarchy of content you’d like to cache on the dispatcher. So.

Whenever a page is access, depending on those rules, page will be cache known. Dispatcher cache. The talk route. And then, One of the key element of dispatcher caching are how do we manage dispatcher caching and then how long. The we. We have a valid content on the dispatcher depends on the stack file level configuration, which can. Be Configured through from file configuration. In the. Dispatcher configurations. And then. Based on that, it create dot stack file and the hierarchy of the page content.

And then The slash cache is the, directive where we will see a list of parts which can be cache for part of this function.

And there are a couple of references, in the documentation. This particular, documentation clearly talks about what kind of what stat file level, values can be defined for a pattern of content or site. And then it really explains with different cache how different stat files, level value, how the cache can get affected.

Yeah. And then there is, there are other, documentation with respect to, dispatcher defining grace period and all.

Okay. So that’s, the list of caching. So if we look at. The, the. Overall architecture, the browser level caching can be managed by using cache control or max H. Header. We can also have ETag in some some cases and which actually used by the we can take a look at.

So. Depending on a max stage value, let’s say if I define max edges 300, 300, which is. 300 seconds. So the the file which is being accessed on the browser resides on the browser cache for five minutes. So any request within that from the same browser, if the user access the same resource, it will be served from. The, Browser cache. So that way. It. I mean, the page load faster for the end user. The. Second one, second layer of caching, which is CDN, even in CDN, you can manage, how long the cache can reside on the screen, at the edge based on caching and on max. So Max each cache control, max edge value is respected by both CDN as well as. The browser. So let’s say if you want to have a different caching.

TTL for CDN, layer on on cloud service, it is fastly, you can have additional header called surrogate control. As. Max edge is basically is going to overwrite max edge value. So you can use surrogate control header to set a specific value to, the fastly, CDN, let’s say on a fast as it, and you want to store the you want to have a cache TTL of like five minutes, right. Which is.

Like, 30 or maybe 300, second. Right. Or if you want, over ten minutes, then you can have 600 seconds. So if you want to have a different value for a browser as well as CDN, you can use cache control as well as surrogate control and the, same dispatcher configuration, which will set the different value. And then the dispatcher, you can have, start file level configured. In the. Form file, which defines what is the invalidation of the content to which level the content validation happens. On. Content hierarchy, which is stored in the dispatcher cache. So we will talk about that in detail. In a second. Okay. So we’ll quickly, look at the demo.

So let’s say I. Have, So this is the, we can side, which is there in my local, Docker. Set up, in my SDK setup in my local. And then, this is the Docker that is, instantiated. So if we look at files in general, the cashier resides under OPD.

So they send anything access has to go to magazine. Sorry. Mount via. HTML content. So if you see. I have the. The USB and access and the magazine. So for that cache is farm to The, the. New page which would be back sitting right. Those sketches, those. Cash flows will be created on the doc road and then, right now. You. Don’t. See, In a stack file open, which is still here. So if I. Let me quickly delete the entire cache and then. Quickly show you, a couple of use cases to, under patched here. Continued.

And then start file. So let’s. Say if I access the adventure page or a magazine. Page, and if I go to content, I have, Actually created that hierarchy adventure. And then I think it can, Yeah.

Okay. So, so it gives. The, I you base health. So let’s say if. I, go to, Cache control, if you look at a, we can, A. Repository that’s default stack files are configured in the set to do, which means that if you publish any page, it is going to create a stack file level until enough to I mean, the level starts from zero.

From HTML content. And then until us you’ll see stack file. So let’s go to A page in my local, Author. And if we go to we can. Yeah. Let’s say I have a magazine. Page, and then I will, and just edit this.

This 18 and then this. So and then I would just. Create, publish once I say publish, if I go. To, the docker.

So you see the stack file level starting from the doc root level, which is where the product, HTML and then. The. First level is zero after that is one and then two until, we can level it. The stack file gets created. Right. So now if you, let’s say if I access, HTML page, right. If I access, magazine page. It is getting, written from the, Cache. So, It’s getting, loaded. So when I update any page, and if I try to replicate a page below, magazine or published adventures, it is going to create a cache, under magazine. And then you are going to have a P, let’s say if I update take surfing page. Right. So if you look at the start file which is generated a one minute ago, and then now if. I, just. Edit this page.

See if I just edit this page and then I just publish this. Now, if you see, the doc and it’s going to match the, the. In that hierarchy, whichever the start file level that defines while propagating, through the parent, Page. So the first stat file that it found, it’s going to, touch it. So what happens with this is irrespective of which page is updated, the stat file is still getting updated at the parent level. And then the content which is there below this entire site or site hierarchy below N is going to get invalidated. So when you try to access a page it’s going to check okay. Stat file level is just that. So it’s going to it’s going to create a cache again and then tell that to the user. So let’s say if I go back and then if I.

Just. Try to check adventures. Right. So before that let me go to Docker and then I open the logs. It’s clear this. And if I just say adventure right. So if you just search for action.

You see the. The cache file is older than last flash, even though the file that. We. Flushed is below. Magazine. And then if I check the entire pages, the adventure page itself got invalidated. Okay. So it is going to create the cache again. And inside of that to the end user. So with this what with this, what we see is that, depending on a start file level, it’s going to check what is the nearest at file level. And then it’s going to, see that okay. After the last type file in that hierarchy everything gets invalidated, even though we just updated a single page. Right. So to avoid this, what we what we encourage the customer is to generally to set probably a hierarchy of 6 to 5, and then if. I, Go back and then just.

Publish, let’s say Was not really a. Page. Okay. So, let’s see if I go here.

So, okay, so if I just open this.

My thing. Western Australia page. And if I go to Docker.

So under Max and you’ll see the Western, Australia. Right. So if I go back to the page and if I.

Just update this page, And if I publish this page and go to the Docker, you see. Now the stack file level is being created and until the level of, magazine. Right. So if you look at zero. 1230123, The under magazine. Yeah. So under until until. Magazine we got this created. So which is. Six. Right. So basically seven six plus seven. So it starts with zero. So it’s going to create a start file level here. Now under a magazine. If I go back and update a page it’s not going to touch the US or Ian level start file level like we have seen before. Okay. So let’s say if I go to San Diego and I. Just update this page.

To let me test.

In to.

Okay. Now if I go back to, and and then in San Diego, if I added this.

And if we quickly publish this.

Okay. Let me test, this type, we can. And yes, an.

If you see this got. Updated 23 seconds ago. So. And any other static level which is above this, it will not get affected. So, I mean. The entire hierarchy gets updated anyway that the latest one got updated here. So anything updating, it’s not going to touch anything. Understand? 511 the same cache can be used. So. So that is the, advantage with having, Hey, Start file level configuration with which you can better manage just, content invalidation and then thereby increasing the cache on the dispatcher. Okay. The the next, layer of, caching is on the dispatch side of CDN. On CD. And there are a couple of use cases where, we have seen with multiple customers in case where they want to use their own CDM and then altogether want to clear the cache on the. Are. Not to use cache on the fastest video. So in that case we can. Have. Cache control or max eight, which defines caching for the, browser, but for fastly, if you want to enable, if you want to use, data, just pass through or, don’t want to cache anything on the fastest hidden. You can use private nocturnal cache for the, surrogate control later, which is going to, not which is not going to allow caching to be done on the, fastly.

Cache and surrogate control is specific to fastly. And then you will not see this in the browser request when it comes to the end user, because it will be shipped off from the, into the the fast delivery. But this is used to define, the caching on the, fastly. So this is normal structure. This basically is location. My directory can be. Generally used in the we use file and define cache control header for each of the resource type like in in my case here I have an example for the HTML like we have for. Any Json case or maybe assets. Generally for asset we have a larger max values like probably ten days or maybe 20 for us. Right. So that is one use case and then stale. While the validator. Would.

Would indicate that okay. Let’s. Have resources access. And then a cache gets created on the hidden cache and then that. The, The TTL for that or maximum value for that is 600, let’s say. Okay. Which is ten. Minutes. So. Enduring after the ten minutes, if somebody tries to access the page, it tries to check whether. Rebalancing is done or not. If it is not done, it is still going to serve the the existing cache file which is present in client. And then asynchronously, it’s going to send the request to the.

To the dispatch CDN. And dispatcher. Am to. Get that cache to val cached file. Back into CDN asynchronously. So, so with this, what happens is even though, it is invalidated, content that is present in client, it still gets heard. And then that way you can have better. Caching or a better performance for the. Page. So these values are generally defined, for most of the static pages of when the latest content being served to the end user is a priority. These values will be much smaller. Or maybe sometimes, you don’t need to add.

So that is one example. Another example is when customers want to have a different, max edge value or a cache value. For. CDN. In. The, fastly as well as on the browser side. So if you look at, in here, we see cache control Max is 6600. But for. Fastly, we are setting that as.

One up, which is 30/602. So with this, what happens is the caching on fastly becomes one hour. So the value with the cached page or cache be sold, which is staring at the edge is going to get cache for one hour. And and but the browser caching will be like use for ten minutes. So this is one way to define different cache values for Browser. As well as CDN. In the demo. Let me quickly. So if we okay. So cache controls for 600 which is ten. And then the target control is set for 30 family, which sounded, one hour on the screen. So if we. Quickly look at the. Demo, let’s say if I go to. CDM. And then if I have. My sandbox.

Yeah. So if you look at this is the, sandbox, that I have. And then if I look at one of the page, I mean, how do you sandbox? Because that’s where, the CD is enabled, right? So if I look at here. The. The cache control header defines, cache control header, which we define in dispatches. I will quickly show that in.

Let’s, if I go to, we can host. Okay. So this is the, The director, which is setting the max age. Sorry.

Yeah, this is the directory that we are using, to set the, cache control Max is standard and then stale while you added 600, for the resource, for the human resources. So if we look at here, this defines what is the.

Max age value. Wait until which the cache value can be sold from the browser cache itself. And then another thing, important thing here is that if you look at X caching, it says hit. That means that. The. The resource which we fetched is being cashed in the client. And then this resource is being served from the student cache. And if I just refresh this page again, you’ll see the same value. And then. Yeah. Yeah. So, so these are the values that you can see, on the browser side with which you can, see, okay. How long the, this is being cached on the browser site.

Cache x cache. And cache control are. The, Two main headers with which you can see whether, partner file is being searched from. She didn’t cache your.

Pay. So if we go back.

Okay, so the the next topic is about, how we manage to dynamic content or if you want to. Filter out the fragment of content from caching. And still. You want to leverage, CDN or despite cash to cache the rest of the static page, or where the dynamic, where the fragment is a dynamic part. So let’s say this. Can be, use. This can apply to use cases like price on a, on a product page, or maybe returning some weather report on a, on a specific page. Right. It can be multiple scenarios. So. The. Using. The, Loading or dynamic content on a page. In M, it. Can be done through two approaches, one is SGA, which is called sling dynamic include which is basically.

Specific dynamic include tag which will be processed separately at the dispatcher. Right. And then this works fine. On the AMS. And then this works on a Cloud service as well. But you have to disable caching of a particular that resource or let’s say HTML, those page needs to be disabled. On the, CDN because if you cache the, pages on the CDN, even the content is dynamic on the dispatcher, it’s being dynamically fetched from the publish. It still is getting cached on this ad, and then the same will be returned to.

To the end. User within that. Message that we. Define. So SCA can still be implemented in cloud service, but it is that we need to disable the caching for that part of page hierarchy in the. CDN using surrogate control, which we saw in that earlier, slides where we can say no cache, no store and private.

And then this is the documentation on the sling dynamic include, which has, very detailed documentation of what are the, what is the configuration that we need to do, and then what is the, budget configuration that we need? Have. So, The another approach to load the dynamic content efficiently on a cloud service is the assigning. So it should include is is a feature that has been recently added, I think last September or October. And then the. The ESR configuration. Can be done. Order needs to be done at the two levels. One is at the OCI. Level where we need to specify that. Okay. But section of the page needs to be dynamic. Right. So that’s part. Part one. The other part, part two is basically how do you process these pages on these CDN. So if. When you, when you include, site component. So the. The steps to the developer essay component is that create a component, try to, render the dynamic content through the component logic. Right. And then.

So for essay we can still use link dynamic include setup where sling dynamic include okay configuration and then part value in the OCI configuration has the option to select as at LSI. So if we look at the next slide the include type can be specified as LSI. So if you have if you’re in general. Building a star component or implementing string dynamic include this particular include ty will be SGA and and sling dynamic include as an option to create essay including the In the page. So so for LSI you will select this as LSI. And then what are the component, dynamic component that you define which renders a dynamic content that needs to be specified in the resource type so that, CDN can recognize, okay, this particular.

Publishing instance can. Identify, okay, this particular section of the page is an essay component. And this needs to be grappled with an essay tag.

So an and rest of the configurations are pretty much similar to SGA. Like no cache is basically used to, segregate the resource type or, or part of this component on the page. So that way we can recognize this particular type in the this pattern and accordingly approach. Okay. So if we come back to the essay, there are a couple of consultation that needs to be, checked before even going with the essay implementation. One is essay tags are processed at the core and sequentially. Not, Concurrently. So having huge number. Or a big. Large number of essay components included in a page is going to add, latency. And that may kind of, slow or have the speed. Of, Bit slow on the end user side. So that is one thing. So try to limit the, the number of essay components on a page. To smaller number. And then a limitation on the maximum depth of essay is three five, because, there are only at a certain level or certain depth that essay components can be. Processed, like let’s say, if we have, one essay component within another essay and then another three, component within that. Right. So that hierarchy, I mean, that includes you can do only till level of five. And. Then other limitation is that the number of essay component that you can include on a page cannot exceed 250. Six.

So that. Is one Consideration before even, you want to consider implementing essay. Okay. So the first part that, like I mentioned, the it’s about configuration of Essay, Essay configuration on the or essay on the publish. So this is the to string dynamic include the essay configuration within which you define that. Dynamic and then within the resource type and then. You define I include type as ASI.

Okay. So, so once this configuration is done, when our page is processed on the publish for the entire dynamic component part, it’s going to generate the essay include tag. And the same thing will be analyzed or processed by CTL. At the edge.

Okay. So the part one is about the configuration. This part two is about the configuration on the.

Dispatcher. Like what are the different configuration that you need to do for a parent page as well as for the, dynamic section of the page? Right. So all the dynamic components are rendered with dot no cache dot HTML extension. Because if you look at. The. Selector that we gave for the CSA component is dot no cache. The the first thing that you need to consider is. Sorry. Okay. The first thing that you need to consider is about the, excuse me essay. You want to make sure that ESR is enabled on the client. So for that, the header that needs to be added for the parent resource is x a site on. And then you also need to make sure that these APIs off between that dispatcher and hidden layer. Because if the Z is done it cannot analyze the ESR tags within the page resource and the CDF. So for that you need to have. Z. Disabled. And then the rest of them are like, what are the, details that you want to define, or cache control header that you want to define for cDNA as well as browser, which are like common configurations for the caching. So these two are important. Configuration one is x ASI as well as Node.js environment variable.

And another one that you need to set is so same compress on. This gets applied once the processing done on the CDN. It’s it needs to compress the page again before it even sends to and use it. So with this you will not have any issue if you don’t set it. But the the the as a compression is not done or which is disable at the dispatcher, the same uncompressed uncompressed. Page. Resource will be will travel through network. And the basically client browser which is.

Which is going to take more time. Right. Than you do a compression. And then for the. Dynamic part of the content, which has dot no dot HTML, which is an essay component within the page that needs to have, zip, disabled as well. So. Nos is set to one, which is true. And then you need to make sure the, the dynamic section of the page, should not be cached on. The, Either on the browser or on the suitcase. So these are the configuration that you need to have. So.

ECS, Amazon and no zip, this is set to true or one. And then. You. Set the am x am in compression header at the parent page level, and then. Set cache control private for that S3 resource for the browser. As well as CDN. And then you define nodes to one.

So these. Are the dispatcher components that you need, for the essay to work.

And then we’ll have Quick, Demo on how this looks on the. Actual browser. So this is my, sandbox. If you look at, magazine. Party. Magazine page, I have a dynamic content. So this is a time. So if you just refresh this. The entire page is getting cached, but, I’ll show that in a minute through our network. But the dynamic part is still getting.

Updated. So if I look at. The overall. Page. If I just refresh this page. And look at the network. It still shows Zcash this hit. Which means that the entire page is still getting cached. On the, CDN. So the cache hit means it’s being served from you didn’t cache. So entire page is still getting cache. And the dynamic part of dynamic part of our page is still getting refreshed.

So so that is the essay component. And then if you want to look at how this looks on the dispatcher. Let me I think.

Okay. Let me. Quickly connect to. VPN and then I’ll. Quickly show you that.

Okay. So meanwhile, I can show you the dispatcher configurations. Which I have. Yeah. So on on my we host.

This is what? This is what are define. Sorry. These are the two sections which defines configurations for the. The. ESR component. So the like I mentioned, the header range is set to zero. And then exam, ESR set on GCP is off. And then we are again compression is setting on at the CDF. And then for the dynamic section we have.

Control set to private. And then nodes is set to one. Okay. So now let me go to.

This I mean yeah. So if I. Go back and then check dot net which actually bypasses the CD layer. And then if I look at. The. So if you look at, you don’t see the dynamic section of the page, then we take component on the page here. Okay. So if I just inspect and then go. To network storage, sorry. If I go to inspect and then if I just say yes, I.

Okay. Quickly.

Okay. So if. You look. At, this is. This is being served from this pattern. So if you look at the cache file on the dispatcher, it has, aeaci included in the page source. And this is being processed by CDN. At the edge when you, try to access that page on the client. Right. So this is a dynamic, content that gets, On the browser. So that is, On the ESR component. And then we’ll also look at couple. Of, Debugging. Approaches on each layer of the browser, this pattern of TDM, to debug the issues on the browser, the, the configuration that you can do is on the network tab, you can disable the cache so that. You rule out a case where that the that is the response that you are getting is from the browser cache. Or you can alternatively use curl command to retrieve. The The headers as well as you can use the private proxying as well. Another approach is to use cache control header. And. You can say no cache max is zero, which is going to bypass the cache here on your browser. And then.

Like the other approach. To by using the response headers, using cache control Max and most other like here. Right. So you can use, max H zero and then no store or no cache.

That way you can invalidate the cache here, or you bypass the cache on the browser and there are certain use cases where if you find out. Or. A session token within the cookies, you that is going to, bypass your browser cache so that maybe, I mean, if you are observing that it is not getting cached from the browser, you can check out whatever cookie are present in, in the cookies are not, You can replicate the browser request by using curl hyphen, hyphen h where you can mention cache control noncash and you can. With this you can fetch all the header request.

Or. Response address as well. So this basically is going to replicate the use case you are accessing from the private browser or like disabling the cache.

Another, Set of debugging, Approaches. Debugging techniques to. To. Debug the caching issue on the CDN is to check what is the X hyphen cache value in your browser. So if the x cache header value. Defines hit miss that surprise. Depending on that, you will see whether that is being served from the dependency. Didn’t cache or not. You can also check CDN log where it will have an attribute of action miss or action hit based on it is being served from the CDN or not.

You can also verify, cache control headers on the dispatcher or on the CDN, custom CDN to see what are the values that are defined.

And you can bypass the CDN by using like from. Cache control, no cache, which is going to bypass you again and then. Provide. You the response. Or you can use. The, Like let’s say if you think it is being fetched from the CDN, you can push the cache on, CDN by using the API or. Or. Maybe the cache control header, Mechanism. The next one is about, how you debug the issues, caching issues on the dispatcher. The first technique would be, would be to define dispatch and log level to debug. So if you if you. Generally don’t make, you don’t generally make this as a debug in production. The use this for a lower environment to debug the issue. You can do that on production as well, but for a very limited time because having a debug level on the. For the dispatch log level is going to write a lot of logs.

And you can check the dispatch have log. Which have Action hit or action miss that define whether a particular value, particular. Resource is being fetched from the dispatcher, cashier, dispatch, dispatches, cache or not.

You can also look at the Http header and Http access. Logs, which basically is going to give you, cache action status. What is the cache action status for resource, whether it is Action hit or is it being served from the, dispatcher or not? It’s a hit or miss will be. Will be present again in this cache action status. And you will also see whether a part of the resource is. Being. Returned 200 or 3, naught 4 or 3, not, that one extra. There. Is. One, approach to it. To check whether a response is retrieved from a dispatcher cache or not. Right. So you can have, slash info being set to one. In, in the. Under the form section. And that is going to enable, a parallel header. It’s going to return Zcash info, which will take a value of a hit or miss. And And this header will be returned in the response headers. When you send a hex hyphen dispatcher I for info header. So I mean it can take any value. Basically you can just say x hyphen dissipates hyphen info set to one. Right. And you can, you can have use this header to set it either through curl command. Or. You can use like mod header, plugins of the browser where you can set this value and then you. Can Debug that.

And then You can use query parameters to bypass the cache, and then but you need to make sure that query parameters are not configured to be cached either on a CD and or on dispatcher.

And you also need to look at like let’s say a parallel value is not being cache. And you you see, cache action as message or maybe in the X cache in for it is mesh. Then you need to check with a parallel resource type that you are accessing. Is is included within a cache configuration. I’m not.

Yes. So that ends. The oral, Presentation. And then we can have. Set of canning.

Yes. Bow and hi. Thank you for the presentation. There is a very common question in the chat. So let me just spit it out to you and you can respond to it. So, the question is dispatcher cache invalidation is based on page activation and CD and cache invalidation is based on the TTL. Is there any solution or best solution to sync the dispatcher cache and screen cache? So whenever the page activation happens same time, the dispatcher cache and screen cache both gets invalidated? So one approach is to and which which we generally recommend is to. Have, Shorter max edge value.

So that way even the cache is updated or even though. Page. Is published and then cache is invalidate on the dispatcher. It’s not going to serve to any request on. The, To any request from the, CD. And before it gets. Stale while invalidate. Right. So while it, it basically is going to fetch and then update this hidden cache, that is one approach. The. Other approach is to use. The, the. CDN, purge API, which is generally used.

On the. On the publisher, on the other people. Right. So depending on of which resource is being published, that resource is being invoked on the page API to invalidate that page on the CDN. So, so that way you will invalidate the page or resource cache at the same time on dispatch as well as on CDN. So that way. And user will request Page. From the publish when the next time when they access. But the cache here is that accordingly, the the max value defined for cache control needs to be managed as well, which should be like a shorter value, because if your browser cache has a ten minutes, right. Let’s say if you set cache control max H to 600, which is a ten minutes within that ten minute window, the the cache is updated. Both dispatch as well as on screen. You still get that from the, browser.

So that is, one cache. One cache VM. Yeah. And there is one more question. So the dispatcher logs are of huge sizes. Do we have any tools that will help to monitor the log real time except ÃÛ¶¹ÊÓƵ IO and the next one. Is there any local tools that help so helps us view the downloaded logs better? So there is, documentation within ÃÛ¶¹ÊÓƵ, at least for m cloud service, you can download the log. There is a I think there is a, there is a tool that we have, that can be used to analyze a log, but at least to, to manage the logs, like, I mean, the size of log that you create. It depends on a layer log level or, or kind of request that we are. Accessing. Right. So the size of that, you cannot, like, you cannot control. But but the, the. The only way that I see most of the customer doing is using, setting up their. Own, Splunk or real K tool. To. Pull the logs from cloud service and then, have report generated on the, Splunk to so that they can analyze the. Logs better and faster.

Anything else? Finish. That’s pretty much I see in the chat and the question section.

Okay. I just see one more question coming in going. So if you are using an API to push the client, how do you how do we know what are the resources to clear other than the page URL? Often images and videos needs to be poised to.

So generally. Generally when you publish a page that is the page that you are going to. Invalidate, right? I mean, if, let’s say the page has, different asset that is being added. So that is B that is going to get reflected on your page anyway when you publish it. So accordingly, that request will be sent to the assets and then fetch it again. Right. So I mean you just need to find out what is the resource that is being published. And then that resource needs to be sent to purge to, clear the cache on CDN.

Yeah. Thanks for one. The next question is can we use SDI on dispatcher and s I on CD and at the same time for the same resource? I think. I think you don’t need that kind of a setup. I’m not sure what is the use case that you are trying to achieve. Generally, you don’t need it. I mean, if you are able to do this through GSI, I would recommend doing that through S rather than including SJ because if you have. Set that. Is. Sent through SDI. In. If you remember the configurations the, the parent level, we define cache control header. Well max value is 600 which is ten minutes. Right. So irrespective of whether you have a Aeaci or SJ component on that, you are going to. Like you. Are going to get cache. I mean, let’s say you define SDA and. You, you. You define, cache control max as 600. And then, even though it is dynamic, it is still going to get cached on the CDN unless you. You. Make sure that you don’t catch that. Right? I mean, you can set a, target control, no cache, comma private if you set that, no caching, for that resource on the client. And then, dispatcher gets, the request gets sent to the dispatcher directly. It doesn’t even. You. Yeah. Yeah. And so this just to add the use case mentioned by mentioned here is because we don’t have CD on localhost. So developer won’t get to see the final result. So that’s the reason this question is. Yeah. So but if you see the read environments also provided with CDN nowadays. So I mean that is that should. So I think you are requirement should drive how you implement. Right. Rather than. The developer comfort. So I think if the requirement is to load the content dynamically, yes. Is the best approach because you can leverage caching at the edge and which is usually much faster than you are getting that, request from dispatcher.

Yeah. So we are on top of time. But there is one last question on when we update a content fragment, how do we invalidate all pages? That is, using the content fragment invalid? The dispatch and and CDN? There is so so. It depends on actually because let’s say your pages for particular hierarchy are using content fragments. Any fragment that is being updated there is a X Commons module which you can use to set the OSA configuration. Let’s say you feel update something in the fragment. You can define okay hierarchy. Let’s say I’m updating content fragment I want slash content slash. We can slash version slash magazine hierarchy needs to be cleared I mean hierarchy that cache needs to be cleared on the dispatcher. So you can have that kind of a rules to, to define through the X Commons configuration. And then that is going to, invalidate the content where. The. Fragments are used. But the disadvantage with that is you are going to invalidate all the.

Magazine pages.

Yeah. That’s that’s all the questions. Bone. Thank you. Okay. Yep. Thank you everyone. Thanks for joining. Have. I’m great. Matt. Thank you.