On Tue, 16 Mar 1999, Mike McCauley wrote:
> 1. Most SQL databases of any consequence have no problem with hundreds of
> thousands or millions of rows. They really are very fast, provided they are
> hosted on a reasonable box (doenst have to be super fast, just 100-200MHz or so
> and a fastish disk), and the indexes are sensibly defined. So a very reasonable
> strategy would usually be to have one accounting table per month or....
*nod* My comments were geared more towards the disk space consumed by
the database than the performance of the db system. Granted, disk space
is really cheap nowadays so my argument gets watered down as each day
passes. Just something in me hates arbitrarialy wasting space by storing
a lot of data that I don't need.
There's an aside to that that's probably more US-centric. I specifically
want to lose the customer-id --> ip address assigned/time-of-day mappings
as soon as possible to protect customer privacy. Courts cannot subpeona
records that don't exist. I figure for troubleshooting and being able to
catch users conducting real attacks, I only need it hanging around for
about a month. If somebody reports that one of my users is attacking
somebody else's network or doing other BadThings, I always get the
report within hours/days/weeks rather than months.
> 4. Lon might be able to use some or all of radacct.cgi for his web page showing
> customer usage.
Oh yeah, already saw that gem. It will definately help when I write my
stuff (CGI is soooo, like yucky man... I'm livin in the late 90's
and have me a nice apache server with mod_perl and mod_asp (which allows
perl *and* asp stuff to be embedded in the page). The OldTime sysadmin
in me will do anything to reduce process-creation overhead. But the
OldTime sysadmin in me also believes that a good way to enhance the
performance of a machine is to quit letting users run programs. Matter
of fact, if we could kick all the users off too..... *grin*).
Lon Stockton
MoonStar
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
