Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • If the Revive Adserver installation is sharing a server with other services, consider if the other services can be moved to another server, to give Revive Adserver a greater share of the server's CPU capacity.
  • If the Revive Adserver database is on the same server as Revive Adserver itself, consider if the database can be moved to another server, to split the CPU used for Revive Adserver from the CPU used for the database.
  • If you are using SQL Local Banners and/or Webserver Local Banners stored in a local directory, consider if these could be migrated to be delivered from an external host - doing so could significantly reduce the CPU use associated with banner delivery. (Alternatively, the use of a CDN service to cache the banners could help.)
  • Consider if running a PHP OPCode cache, which will cache a "compiled" version of the code, to save on CPU time when running the scripts, is appropriate.

...

  • If the Revive Adserver installation is sharing a server with other services, consider if the other services can be moved to another server, to give Revive Adserver a greater share of the server's memory capacity.
  • If the Revive Adserver database is on the same server as Revive Adserver itself, consider if the database can be moved to another server, to split the memory used for Revive Adserver from the memory used for the database.
  • If you are using SQL Local Banners and/or Webserver Local Banners stored in a local directory, consider if these could be migrated to be delivered from an external host - doing so could significantly reduce the memory use associated with banner delivery. (Alternatively, the use of a CDN service to cache the banners could help.)

Otherwise, you may need to consider upgrading your server to add more memory capacity.

...

  • If the Revive Adserver installation is sharing a server with other services, consider if the other services can be moved to another server, to give Revive Adserver a greater share of the server's disk I/O capabilities.
  • If the Revive Adserver database is on the same server as Revive Adserver itself, consider if the database can be moved to another server, to split the disk I/O for Revive Adserver from the disk I/O for the database.
  • If you are using SQL Local Banners and/or Webserver Local Banners stored in a local directory, consider if these could be migrated to be delivered from an external host - doing so could significantly reduce the disk I/O associated with banner delivery. (Alternatively, the use of a CDN service to cache the banners could help.)
  • Consider if the Banner Delivery Cache settings are appropriately set - a higher cache time will mean fewer disk I/O accesses to retrieve banner details from the database.
  • Consider if the Banner Logging settings are appropriate - in particular, note that logging requests as well as impressions effectively doubles the number of records recorded for each banner delivered, compared with just recording impressions.

Otherwise, you may need to consider upgrading your server to add more disk I/O capacity.