Comments on: Performance Tuning http://blog.openx.org/06/performance-tuning/ OpenX Community News Fri, 21 Nov 2008 23:47:59 +0000 http://wordpress.org/?v=2.6.2 By: OpenAds performance tuning at btard deleted nostatus http://blog.openx.org/06/performance-tuning/#comment-28275 OpenAds performance tuning at btard deleted nostatus Wed, 16 Jan 2008 08:43:48 +0000 http://blog.openads.org/06/performance-tuning/#comment-28275 [...] OpenAds Performance Tuning. Great article on Performance Tuning of OpenAds. [...] [...] OpenAds Performance Tuning. Great article on Performance Tuning of OpenAds. [...]

]]> By: Mayavi http://blog.openx.org/06/performance-tuning/#comment-7458 Mayavi Tue, 25 Sep 2007 08:44:33 +0000 http://blog.openads.org/06/performance-tuning/#comment-7458 Hi David. You can find the documentation for installing distributed stats. https://developer.openads.org/wiki/DistributedStats You will need time to implement this ...but believe me this works best for high volume serving. Hi David.

You can find the documentation for installing distributed stats.

https://developer.openads.org/wiki/DistributedStats

You will need time to implement this …but believe me this works best for high volume serving.

]]> By: David http://blog.openx.org/06/performance-tuning/#comment-2033 David Thu, 19 Jul 2007 02:34:48 +0000 http://blog.openads.org/06/performance-tuning/#comment-2033 Andrew, Is there any documentation that explains the "distributed statistics" deployment option? David Andrew,

Is there any documentation that explains the “distributed statistics” deployment option?

David

]]> By: Andrew Hill http://blog.openx.org/06/performance-tuning/#comment-716 Andrew Hill Tue, 12 Jun 2007 06:26:23 +0000 http://blog.openads.org/06/performance-tuning/#comment-716 Writing to a syslog facility is an interesting idea, and one that we have considered for Openads. The reason we haven't implemented it ourselves is that Openads 2.3 supports conversion tracking, and to do that effectively, a syslog of the raw data won't do the job. Instead, for really large setups where a single core database isn't fast enough, Openads has support for "distributed statistics" - where every web server in your cluster runs a slave database (a partial replication of a core database). Each web server then logs its own statistics to the local database, and performs a partial statistics summary locally. This data is then pushed to the core database, where the remaining statistics generation that requires a complete view of the raw data can be performed. Writing to a syslog facility is an interesting idea, and one that we have considered for Openads. The reason we haven’t implemented it ourselves is that Openads 2.3 supports conversion tracking, and to do that effectively, a syslog of the raw data won’t do the job.

Instead, for really large setups where a single core database isn’t fast enough, Openads has support for “distributed statistics” - where every web server in your cluster runs a slave database (a partial replication of a core database). Each web server then logs its own statistics to the local database, and performs a partial statistics summary locally. This data is then pushed to the core database, where the remaining statistics generation that requires a complete view of the raw data can be performed.

]]> By: justin http://blog.openx.org/06/performance-tuning/#comment-712 justin Tue, 12 Jun 2007 01:03:32 +0000 http://blog.openads.org/06/performance-tuning/#comment-712 <blockquote>Openads delivers content to web sites, for sure, but most of the real load comes from logging all those impressions and clicks.</blockquote> we run a dedicated Openads db with 3 load balanced php servers handling delivery, and have noticed just how intensive the db writes are. we're at about 20 writes a second on average (peaking at around 40 writes a second), and are looking to scale this out further and considering other ways to keep the stats. one implementation that occurred to me is to write the raw stats to a syslog facility instead of the db, and have the processing scripts run over these logs to produce statistics, would the Openads team be interested in patches to implement such a feature?

Openads delivers content to web sites, for sure, but most of the real load comes from logging all those impressions and clicks.

we run a dedicated Openads db with 3 load balanced php servers handling delivery, and have noticed just how intensive the db writes are.

we’re at about 20 writes a second on average (peaking at around 40 writes a second), and are looking to scale this out further and considering other ways to keep the stats.

one implementation that occurred to me is to write the raw stats to a syslog facility instead of the db, and have the processing scripts run over these logs to produce statistics,

would the Openads team be interested in patches to implement such a feature?

]]>