----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Bernd Jagla" <[EMAIL PROTECTED]> Cc: "mysql" <[EMAIL PROTECTED]> Sent: Tuesday, March 02, 2004 3:43 PM Subject: Re: no one can log on any more
Are you sure you allotted 512MB for both read_buffer and sort_buffer_size? Try reducing these values so that the total is roughly 80 percent of your total physical memory. >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 3/2/04, 2:26:31 PM, Bernd Jagla <[EMAIL PROTECTED]> wrote regarding Re: no one can log on any more: > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: "Bernd Jagla" <[EMAIL PROTECTED]> > Cc: "mysql" <[EMAIL PROTECTED]> > Sent: Tuesday, March 02, 2004 3:14 PM > Subject: Re: no one can log on any more > The database server becomes unresponsive to new threads? > What is the result of the following equation? > key_buffer_size + ( (read_buffer_size + sort_buffer_size) * max > _connections ) > 256 +((512 +512)*100)=100.25Gb > Yup, thats bigger that our physicall memory (100 Gb > 8 Gb)!!! > So I guess that might be the problem.... ;-) > Does the i/o error also relate to this problem? > Is this larger than you physicall memory? So I changed the variables now: 512M + (8M +8M)*100 = 2.1Gb Still same problem. But now the distinct works. I still can't log on when both queries are running.... B -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
