3 million pages per hour

Caching for performance

Performance is getting more and more important for both user experience and google search rankings. Most dynamically built CMS driven sites will not meet the same speed and performance of a statically served sites.

There are a few strategies to get around this, one of them is caching. Caching is when a site build HTML then holds the result in a fast 'cache' in memory.

In many cases this requires configuration and management. fw8 native cache handling is totally management free across multiple servers.

In 2010, Google did something different. Google announced website speed would begin having an impact on search ranking. Now, the speed at which someone could view the content from a search result would become a factor.

In a recent performance test we showed an AWS t2.medium serving 1000 pages per second with a page speed of around 30 milliseconds.

See the video.