public inbox for [email protected]  
help / color / mirror / Atom feed
From: Marc G. Fournier <[email protected]>
To: Dave Page <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: Dumping the banner ads
Date: Wed, 10 May 2006 09:24:04 -0300 (ADT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E40138802B@ratbert.vale-housing.co.uk>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E40138802B@ratbert.vale-housing.co.uk>

On Wed, 10 May 2006, Dave Page wrote:

>
>
>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of Josh Berkus
>> Sent: 10 May 2006 07:19
>> To: PostgreSQL WWW
>> Subject: [pgsql-www] Dumping the banner ads
>>
>> Marc, could you please acquaint us with the outstanding
>> obligations with the banner ads?  Whom have we promised what?
>>  Who will we owe refunds to?
>
> I cannot speak for the paid ones, but we have always offered our mirror
> providers a free ad - there certainly should be a few of those still in
> the system. We might find we cheese off a few of them by removing the
> ads.

Right now, we have active:

CommandPrompt    - Mirror/Free
EnterpriseDB     - Expires June 18th
ExtendDB         - Expires May 15th
Navicat          - Expires July 4th
Pervasive        - Mirror/Free
PgAdmin          - OSS Project/Free
Sam's Publishing - Exchange program for 'Show Books'

Navicat runs until July 4th, everyone else expires earlier then that ... 
so we can scheduale dumping them on the 4th of July ...

Personally, the use of MySQL vs PostgreSQL for banner ads is 'using the 
right tool for the job' ... Banner ads aren't "data integrity heavy", who 
cares if you lose a click or impression here or there in the stats?

Just to put things into perspective ... the banners used to run on a 10 
line, homegrown script that did nothing more then keep track of # of 
impressions ... pg_autovacuum ran almost continuously on the one table 
that did "UPDATE counter SET cnt = cnt + 1 WHERE banner_id = #" ... and 
the counter table was purely "banner_id, cnt" ... switching over to 
phpAdsNew allows ppl login to an interface and see extended statistics 
like countries ppl are clicking in from, etc ... and performing better 
then the '10 line script' did ...

As for Josh's comment about "switching to a mysql platform while we 
weren't looking" ... nobody ever asked what the backend was ... everyone 
was complaining that the banners weren't loading fast enough, so I fixed 
that situation *while* extending the functionality of the system so that 
more detailed statistics were being maintained ... and I wasn't going to 
lie about what we were using ...

Matteo asked what we were using on -advocacy, and, IMHO, it would have 
been suspicious if, after you pointedly asked me to confirm, the query 
went un-answered ...

PostgreSQL is a steady workhorse, but there are at least 2 things that 
I've found it doesn't do well: banner ads and bayesian database :(

----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email: [email protected]           Yahoo!: yscrappy              ICQ: 7615664



view thread (14+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Dumping the banner ads
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox