Cofax logo

Welcome to the web site 
AboutTechnologyDownloadCofax in ActionContactsDevelopmentDocumentationSite map
0 > Home > Documentation > Installation Instructions > Recommendations for Hosting Cofax for High Scalability print this email this   

Recommendations for Hosting Cofax for High Scalability

Out of the box, Cofax provides a highly tunable cache to provide scalability for most low traffic sites. Follow the recommendations below to achieve the scalability required for sites like the Philadelphia Inquirer. Below I will describe a series of levels to use to scale up for varring degrees of performance requirements.
  • Level 0 - Tune Tomcat, JVM, and database, to use memory efficiently. Tune cache parameters in $TOMCAT_HOME/webapps/content/WEB-INF/web.xml to cache as many pages and templates as memory allows. Note, typically the templates and packageTag caches can be tuned to low figures (under 200 to track and cache), since the db contains fewer then 200 packageTags and even the Philadelphia Inquirer, the most complicated Cofax site yet launched, utilized less then 100 templates. Most sites get by with 4 to 8 templates.
  • Level 1 - Seperate the layers vertically . Follow the recommendation above to host the Editor's Tools (CMS) on a seperate machine. Host the database on a seperate machine. Install Apache on an additional machine. Move static resources from Cofax to be served by Apache directly. Edit $TOMCAT_HOME/webapps/content/WEB-INF/web.xml and edit init-param configGlossary:staticPath so templates will access images and other static data from this new relative URL path.
    • Cofax Page: UserBrowser->ApacheServer->CDSTomcatServer->Database1
    • Static Resources: UserBrowser->ApacheServer
    • Content Management: EditorBrowser->CMSTomcatServer->Database1
  • Level 2 - Seperate the layers horizontally.

    More notes to come.


    Powered by Cofax - Please see for more information.

    Valid HTML 4.01!    Valid CSS!