My dear friend,
Mounting more RAM, your friend don't must expect at "miracles". A server
machine (like your friends) will should run "easily" more then 20
concurrent users.
Your friend have a different kind of problem.
I think it's better to monitoring users activity using "top" utility.If are
threads/processes which "eat" too much "%MEM" and is no activity at "%CPU"
then it's OK,RAM is needed(sincerly, for me it's hard to believe).But in the
reverse case... or your friend has too big database and another machine is
required, or it's something (database design point of view)fundamental
wrong.
Best regards,
Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY
Permanent e-mail address : [EMAIL PROTECTED]
[EMAIL PROTECTED]
----- Original Message -----
From: "Stefan Hinz" <[EMAIL PROTECTED]>
To: "Gelu Gogancea" <[EMAIL PROTECTED]>; "Nilesh Shah" <[EMAIL PROTECTED]>;
"Jared Richardson" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, June 11, 2002 11:26 PM
Subject: Re: mysqld refusing connections while getting sloooow
> Dear Gelu,
>
> > This is a specific behaviour for tables which are not properly indexed.
>
> Looks like my friend needs more RAM and better indexing :-)
>
> Thanks!
>
> Regards,
> --
> Stefan Hinz <[EMAIL PROTECTED]>
> CEO / Geschäftsleitung iConnect GmbH <http://iConnect.de>
> Heesestr. 6, 12169 Berlin (Germany)
> Telefon: +49 30 7970948-0 Fax: +49 30 7970948-3
>
>
> ----- Original Message -----
> From: "Gelu Gogancea" <[EMAIL PROTECTED]>
> To: "Nilesh Shah" <[EMAIL PROTECTED]>; "Jared Richardson"
> <[EMAIL PROTECTED]>; "Stefan Hinz" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Tuesday, June 11, 2002 9:16 PM
> Subject: Re: mysqld refusing connections while getting sloooow
>
>
> > Hi,
> > My opinion is:
> > This is a specific behaviour for tables which are not properly indexed.
> >
> > Regards,
> > Gelu
> > _____________________________________________________
> > G.NET SOFTWARE COMPANY
> >
> > Permanent e-mail address : [EMAIL PROTECTED]
> > [EMAIL PROTECTED]
> > ----- Original Message -----
> > From: "Nilesh Shah" <[EMAIL PROTECTED]>
> > To: "Jared Richardson" <[EMAIL PROTECTED]>; "Stefan Hinz"
> > <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > Sent: Tuesday, June 11, 2002 9:36 PM
> > Subject: RE: mysqld refusing connections while getting sloooow
> >
> >
> > I think increasing memory and giving more memory to MySQL would help.
> >
> >
> > Nilesh
> >
> > -----Original Message-----
> > From: Jared Richardson [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, June 11, 2002 1:48 PM
> > To: Stefan Hinz; [EMAIL PROTECTED]
> > Subject: Re: mysqld refusing connections while getting sloooow
> >
> >
> > We've seen very similar behavior when there are very long SQL queries
> > being
> > run that are disk intensive.. generally speaking, something is having to
> > traverse the table (or a temp table) line by line. If he has any
> > logging
> > capability, see long each SQL query is taking to return to his app then
> > clean up the "bad" ones.
> >
> > Also, look at faster disks... 7,200 rpm, bigger internal caches (some
> > disks
> > have 8 meg!), small raids are inexpensive, and you can put different
> > tables
> > on different physical disks to speed access.
> >
> > Oh yeah, with MySql, you can put all the temp tables on a different
> > disk.
> > We found this to make an amazing difference!
> >
> > Also, a P4 or an Athlon system is a great deal faster than your friend's
> > system... the faster bus speeds on those architectures will again make a
> > huge difference. We buy dual Athlons with a gig of ram for about 2
> > thousand
> > dollars.
> >
> >
> > ----- Original Message -----
> > From: "Stefan Hinz" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, June 11, 2002 12:30 PM
> > Subject: mysqld refusing connections while getting sloooow
> >
> >
> > | Dear list,
> > |
> > | a friend of mine asked for assistance on the following problem (which
> > I
> > | cannot solve myself):
> > |
> > | He has a mysqld 3.23.38 running on Linux, with 2 cpus (400 MHz
> > celeron)
> > | and 512 MB ram. mysqld runs as a production server, with some
> > | applications running about 80 queries per second. There are about 20
> > | concurrent connections per hour. He uses myisam tables, no innodb or
> > | something.
> > |
> > | Quite often he finds that new clients (apps) cannot connect to mysqld,
> > | the connection is refused. My friend tried to connect from localhost
> > to
> > | mysqld once when this happened, trying to log in as admin. Even for
> > him,
> > | the connection was refused by mysqld (although mysqld is supposed to
> > | keep one connection open for the admin, in any case). To be correct
> > | about this, mysqld didn't respond at all, for 5 minutes.
> > |
> > | When connections for new users (apps) are blocked by mysqld, he finds
> > | that response times will slow down by factor 20, for users that are
> > | connected at this time. Also, he finds that Linux will kill mysqld
> > | *sometimes* (the server is re-started automatically).
> > |
> > | I did not find anything unusual using mysqladmin extended-status or
> > | mysqladmin variables. In my.cnf however, I found something strange:
> > |
> > | [mysqld]
> > | ...
> > | skip-locking
> > | set-variable = key_buffer=256M
> > | set-variable = max_allowed_packet=1M
> > | set-variable = table_cache=256
> > | set-variable = sort_buffer=1M
> > | set-variable = record_buffer=1M
> > | set-variable = myisam_sort_buffer_size=64M
> > | set-variable = thread_cache=8
> > | # Try number of CPU's*2 for thread_concurrency
> > | set-variable = thread_concurrency=8
> > | log-bin
> > | server-id = 1
> > |
> > | If I count these buffers and caches, this will add up to > 320 MB plus
> > | the table cache. Could this be the cause of the problem, when my
> > friend
> > | only has 512 MB of RAM on the machine?
> > |
> > | Any help is greatly appreciated.
> > |
> > | Regards,
> > | --
> > | Stefan Hinz <[EMAIL PROTECTED]>
> > | Geschäftsführer / CEO iConnect GmbH <http://iConnect.de>
> > | Heesestr. 6, 12169 Berlin (Germany)
> > | Tel: +49 30 7970948-0 Fax: +49 30 7970948-3
> > |
> > |
> > | ---------------------------------------------------------------------
> > | 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
> > |
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
>
>
---------------------------------------------------------------------
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
