Performance

This is a simple module that moves all JavaScript

EdgeCast CDN is a high performing CDN that is great to work with Drupal. This module attempts to help to integrate the EdgeCast CDN into your drupal site. This module helps you employ some of the custom features of EdgeCast that you cannot get from the CDN module.

Currently these are the features this module offers:

• Manual purging of content
• Reports dashboard to show metrics from your account
• Token Authentication

Token Authentication (Token Auth) is an optional service from EdgeCast that allows you to protect content. A token (appended to the end of a file name as a query string) is required to access the content. This very function allows for you to protect digital content. This module was written around a need for this as it was being developed for a website that offered purchased digital downloads. We couldn't have links being shared on the Internet to access files that require a purchase.

This supports Token Authentication via one of two ways: via a web service call or via a php module. The later of the two is the quickest method of course; however, this module (ectoken.so) is only available through your sale agent. I will explore packaging the php module with the Drupal module if Edgecast will approve of it.

A simple profiler focused on giving an overview of various central parts of drupal.

This module is intended to be used as an APC opcode cache flush automator for high performance Drupal-setups.

If you have setup PHP with apc.stat=0 in production and you deploy code updates (with version control or CI or whatever) you need to either restart your webserver or restart php-fpm to flush the opcode cache. You could also execute apc_clear_cache() with a script.

This task becomes more complicated when you have multiple webfronts. All servers need to flush in sync - or they will execute different code, which will mess up everything. Also, doing webserver restarts theorically might abrupt current http requests, while apc_clear_cache() doesn't.

How to use

This module integrates with standard Drupal cache clear and drush. To flush caches (for one or more servers) with drush, you can run:
drush cc all or drush cc apc

When to use

This module is useless for you, unless you have configured your production PHP server(s) with apc.stat=0!

Code deployments to production should usually/always end up with a global cache clear, and the cache clear integration makes things work mostly out of the box. There are some special cases such as when the site is in maintenance mode, but those challenges can be circumvented.

Why to use

Switching to Drupal 7.50 makes this module obsolete, the performance issue was fixed in that version of Drupal core.

You need no longer bother yourself with caching strategies - which view is cached and for how long, how panels are cached.