Hi,

Hm, using ulimit on my own Ultra Sparc w/ Solaris 8, I can raise ulimit
to max. 1024. Probably not quite enough. More study will be required :-/


Martijn

> -----Original Message-----
> From: Gleb Paharenko [mailto:[EMAIL PROTECTED] 
> Sent: donderdag 23 juni 2005 16:27
> To: mysql@lists.mysql.com
> Subject: Re: Increasing max_connections and table_cache on Solaris 8
> 
> Hello.
> 
> I don't have enough experience with Solaris.. But on most 
> Unixes your could change the limit of file descriptors for 
> process, not for whole system.
> 
> See:
>   http://dev.mysql.com/doc/mysql/en/not-enough-file-handles.html
> 
> 
> 
> "Martijn van den Burg" <[EMAIL PROTECTED]> wrote:
> > Hi,
> > 
> > This applies to 4.1.10 on Solaris 8, with 1 GB of RAM.=20
> > 
> > Our internal customer wants to be able to make 1000 concurrent 
> > connections to our database, with a mix of MyISAM and 
> InnoDB tables, 
> > but according to http://dev.mysql.com/doc/mysql/en/table-cache.html 
> > and an online Solaris reference 
> > 
> (http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SOLTUNEPAR
> > AM
> > REF/p44.html) I would need a table_cache of roughly 
> 1000*2*3 =3D 6000 
> > (assuming only MyISAM tables are used which need two file 
> descriptors 
> > per table, and three tables per join).
> > 
> > However, from experience I know that increasing table_cache 
> from 64 to
> > 256 will already result in 'Too many open files' errors and the 
> > database becoming unaccessible.
> > 
> > To solve this, and actually allow 1000 connections, should 
> I let the 
> > sysadmin increase the limit of open file descriptors on the Solaris 
> > box, or is there a setting in MySQL that I overlooked?
> > 
> > Note: max_connections is set to 1000 in the my.cnf file, but when 
> > starting up, MySQL doesn't accept that value and decreases 
> it to 246.
> > Setting the variable to 1000 whilst MySQL is running /is/ accepted.
> > 
> > 
> > Kind regards,
> > 
> > --
> > Martijn
> > ASML ITM&S Application Support / Webcenter


-- 
The information contained in this communication and any attachments is 
confidential and may be privileged, and is for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify the sender 
immediately by replying to this message and destroy all copies of this message 
and any attachments. ASML is neither liable for the proper and complete 
transmission of the information contained in this communication, nor for any 
delay in its receipt.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to