Hello.
On Sun, Apr 14, 2002 at 11:16:02PM -0400, [EMAIL PROTECTED] wrote:
> On Sun, 2002-04-14 at 22:17, Craig Westerman wrote:
> > I'm needing counter for site that receives 80 to 120 hits a minute at peak
> > load. Many I
[...]
> I personally wouldn't recommend logging to mysql. 80 to 120 queries
> a second
Please note that he talked about minutes and not seconds. Yes, I
wouldn't call 100 hits a minute a high load server, either. :-)
> would overload a db server.
Sorry? I dare to differ. Because I can do something like about 5.000
inserts/sec on my production machine, I did a small test:
On my slower development machine[1], I can execute about 3800 dummy
queries[2] or 1800 counter updates[3] per second.
So no, 80-120 queries/sec don't overload a MySQL server. They only do,
if they are more complex and not a simple counter. Of course, that
wouldn't allow for an equivalent of 1800 page hit because there is
other work involved. But, well, you were talking about the MySQL part
being too slow.
Because the same machine serves about 125 static pages/sec[4] with
Apache 1.3.12, I would say the bottleneck is not with MySQL.
Bye,
Benjamin.
[1] PIII 450MHz, 384MB, IDE disk
[2] SELECT 1, measured with 100.000 queries
[3] UPDATE login SET last_count=LAST_INSERT_ID(last_count+1) WHERE gid=<id>
with random(!) ids to a table with about 330000 entries (i.e. one
of 330000 counters!).
[4] measured with 10 concurrent clients making each 1000 hits; btw,
less than I had guessed.
--
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
