Use a separate DB for something like this - have a data database, and a 'logging'
database.  We're setting up something similar - currently we have 2 databases for
separate things, and will probably merge the first two datasets back into the main
database, and turn the second one into a logger.



Alex Black wrote:

> the problem with that is as soon as you run a load-baanced installation,
> collecting apache logs start to be a pain in the a$$ :)
>
> I have given some thought to the logging thing, but am still undecided re:
> letting apache do its thing, and writing scripts to aggregate the logs, or
> turning off apache logging and going to the DB.
>
> problem is this puts an annoying amount of stress on the production DB, so
> there you have it, the dilemma :)
>
> -a
>
> --
> Alex Black, Head Monkey
> [EMAIL PROTECTED]
>
> The Turing Studio, Inc.
> http://www.turingstudio.com
>
> vox+510.666.0074
> fax+510.666.0093
>
> Saul Zaentz Film Center
> 2600 Tenth St Suite 433
> Berkeley, CA 94710-2522
>
> > From: [EMAIL PROTECTED]
> > Newsgroups: php.general
> > Date: 14 Jan 2001 01:58:33 -0800
> > Subject: Re: [PHP] logging page views, which method is better????
> >
> > Addressed to: "Dallas Kropka" <[EMAIL PROTECTED]>
> > [EMAIL PROTECTED]
> >
> > ** Reply to note from "Dallas Kropka" <[EMAIL PROTECTED]> Sun, 14 Jan 2001
> > 00:57:10 -0600
> >>
> >>
> >> I have a large site, with several hundred pages.... its a product
> >> listing and shopping cart.... and I want to log my page views.... I
> >> receive an average of 3000 hits per minute.
> >>
> >> Is it better (faster) to log my views to a database table? or to a
> >> flat file?
> >
> >
> > No need to re-invent the wheel, all accesses are already being logged.
> >
> >
> > If you are using Apache, take a look at the access log.  Every hit to
> > the server is already logged there.  I am not sure what the default
> > location for the file is, but you can find it with
> >
> > locate access_log
> >
> > or by looking for the string  Log  in your httpd.conf file.  I believe
> > it may appear under either the AccessLog or CustomLog keywords.
> >
> > You might want to look at Webalizer, or a couple of other programs to
> > analyze the contents.
> >
> > http://www.mrunix.net/webalizer/
> >
> > There are others, but this is the one I use.
> >
> >
> >


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to