LiveSite Mechanism

Hi,

I would like to ask about LiveSite mechanism and how it works. From my understanding, LiveSite has a cache system that will create the cache file for a .page during the initial time .page arrives in the Runtime server. And the cache will not be cleared until the .page is updated. Is this correct?

So whenever a user access the webpage, it will get from cache and Not generate the whole page again, right?

In our case, .page has components which refers to contents.xml from templatedata folder. During runtime when 1st user access this .page, will it load everything from cache or does it have to go to templatedata, fetch the content.xml and display? After that when 2nd user comes and access the page, does it fetch everything all over again or take it from cache? Does my question earlier applies to this condition?

Please help clarify.

Thank You!

Find more posts tagged with

Comments

Migrateduser

Sitepublisher gives granular control on caching at component level. Check the cache time settings on a component that you put on a page. It can vary from Until Published (Default) to never.

---Note from Site Pub 7.2 Documentation---
Cache Time menu-> This setting is very important for runtime performance. It specifies how often the component communicates with the server to refresh its data. In general, set the cache time for most components to Until published (default), and rarely set it to Never. Components that have form submissions or display dynamic data, such as news feeds or stock quotes, should be cached at regular intervals. For example, you might set the cache time for a component that receives updated news feeds to 10 minutes. Doing so ensures that the component refreshes only six times an hour. You should match the cache time to the data refresh rate. If the cache time is set to Never, the server could receive an unlimited number of requests.

jihan

Hi,

Thank you for your reply. Our components are now set to Until Published, and our during deployment, will send over a cache.xxxx file for the Invalidation Runtime Cache to run.

So by this, I take it that LiveSite is running with cache.

What about "In our case, .page has components which refers to contents.xml from templatedata folder. During runtime when 1st user access this .page, will it load everything from cache or does it have to go to templatedata, fetch the content.xml and display? After that when 2nd user comes and access the page, does it fetch everything all over again or take it from cache? Does my question earlier applies to this condition?"

Thank You

RonaldV

Hi Jihan,

caching is an *undocumented* feature of Livesite so your question is a valid one. (IMHO LiveSite is an undocumented feature of Teamsite :-).

I believe that Livesite caches the whole result of the page-rendering. Thus, in the case where:

.page + dcr = html-result

it would cache the html-result. And would you modify the dcr and not refresh the cache the modification would not show.

Given this it is very simple to test: do a page-request, change the dcr (directly on the livesite-server!!!) and do the same page-request.

@Iwov: why is the caching-mechanism not documented???

tabletest.GIF

jihan

Hi RonaldV,

Thank you for your reply. I have to agree that LiveSite is not much documented, especially on this issue.

Anyway, as the result of the simple test you've suggested, I can't see the content changes when cache is not updated. So it shows that LS caches the html-result, as in the whole page, and will not get the content everytime there's a user request.

Thank You.