On Sep 22, 2006, at 1:35 PM, Drew Wilson wrote:
Have you looked at pgLOGd? Or its successor, dbWebLog?
Both of these claim to offer low-overhead robust logging.
yeah. no dice.
the problem isn't about the overhead on apache-- its about the
overhead of the database. i believe pgLogD used a buffer to queue
logging items, but had an db connectivity issue.. and dbWebLog was
trying to address that.
but they both run into the issue of: your server gets slammed and
you're continually doing db writes
for a page content server, any of these options would be fine.. but
this is for a syndicated content server. its just tossing out 5 files
- but onto other sites - as it does a lot of hit-tracking. in
private beta, its only serving 20k day -- which is more than fine for
any of those issues. but i'm looking at going into public beta next
week, and i fear that for my db.
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
