Loading ...
close

Would you like to discuss your environment with a knowledgable engineer?

Preferred communication *

Thank you. We will be in touch with you shortly

Archive

  • User Agent based caching

    Posted by on October 25th, 2010

    aiCache now has the capability to add User Agent string to signature of cacheable responses. By default, Aicache uses hostname  and URL of request, possibly sanitized by removing some parameters or discarding the complete query string, as a signature of (pointer to) cached responses. Some sites might serve different cacheable content in response to requests for […]

    read more
  • Troubleshooting 101 with aiScaler

    Posted by on October 25th, 2010

    You’re in charge of a complex web site with a multitude of sub-domains, hosting all kind of information: editorial news, search, viewer comments, videos, news feeds, financial stock quotes. It is a thing of beauty, with 20+ APIs of all sorts, few dozen web, application and database servers – all working in concert to drive […]

    read more
  • Clustering aiScaler: United We Stand …

    Posted by on October 25th, 2010

    Most web site deploy aiCache in multiples, for a number of reasons. Even if your site’s traffic doesn’t warrant multiple Aicache servers, you’re still advised to have at least two, so that one can go down or be taken down for maintenance, without affecting the site. With more than one aiScaler server deployed, it makes […]

    read more
  • Configuring Client-to-Origin Server Persistence.

    Posted by on October 25th, 2010

    Some sites have a need to “pin” clients to specific origin servers. For example, a client A might need to be pinned to origin server 1, client B to origin server 2, while client C might be served by any available origin server. The reasons for such configuration may vary but a common theme to […]

    read more
  • Front-ending with aiScaler, the additional benefits.

    Posted by on October 25th, 2010

    With aiCache front-ending client requests – receiving and processing them before they ever get to your origin web server, Aicache is capable of providing even more benefits. Enforcing time, size and sanity limits on requests. Due to extremely efficient,  non-blocking multiplexed IO model of aiScaler, it is ideally suited to front-end user traffic , while […]

    read more
  • Stayin’ alive…

    Posted by on October 25th, 2010

    An all too common web site failure is overwhelming (running out of space on) log partition. It can happen due to a failure to rotate and offload log files, unexpected spike in traffic and similar conditions. A normal reaction to such out-of-space condition is  for web server to abort serving requests (exit) and hope that […]

    read more
  • Cache size management via query parameter busting.

    Posted by on October 25th, 2010

    You can also keep some of the parameters in the query portion of the URL, while removing others. Such modification only affect the cached response’s signature and have no effect on anything else. Again, this is done to optimize performance and reduce waste that would occur otherwise. Let’s consider this URL: www.acmenews.com/showstory.asp?storyid=1234&partnerid=partner1 We must use […]

    read more
  • aiScaler Cache size management via Cache-by-Path Feature.

    Posted by on October 25th, 2010

    If your web site is fairly large and has significant number of various Web documents (URLs), after deploying aiScaler, most of the content from your web servers will end up in the aiScaler’s response cache as users request it from your web site. aiCache is designed to keep such cacheable responses in  memory (RAM) and […]

    read more
  • aiScaler Header-driven cache invalidation example

    Posted by on October 25th, 2010

    The Header-driven Cache Invalidation. This feature is best explained by an example. Let’s say you have a message board web site where you want to cache discussion threads and forum fronts. Yet at the same time, when a new message is added to the thread, you want to content of the respective discussion thread to […]

    read more
  • Cacheable and non-cacheable content and why very large TTLs are not always a good thing.

    Posted by on October 25th, 2010

    When aicache is concerned, content can be divided into 2 broad categories: cacheable and non-cacheable . It also helps  to think of cacheable content as one that can be shared and non-cacheable content as one that should never be shared or offers no merits when cached. Certain content on your web site might  change frequently, […]

    read more