I was getting a little OT there Gaspar.

It might be better for me to file a feature request on mysl 
bug reporting page for any un-necessary functionality and 
the associated documentation to be removed from mysql 
in version 6.0.x, rather than hijacking this thread!

Regards

Keith


On Sun, 11 Jun 2006, Gaspar Bakos wrote:

> To: Keith Roberts <[EMAIL PROTECTED]>
> From: Gaspar Bakos <[EMAIL PROTECTED]>
> Subject: Re: my-huge.cnf quite outdated
> 
> Hi, Keith,
> 
> RE:
> > This seems to be the way things are with mysql nowdays.
> > Is it not time for the developers to take a serious look
> > into culling all the outdated and multiple ways of
> > accomplishing the same thing from mysql and the
> > documentation?
> 
> This is a somewhat different subject.
> But you are right about it.
> 
> On the other hand, I have been using MySQL since 2001, and I enjoy
> looking at the old syntax, and seeing how it changed helps me
> understanding what the new syntax means.
> 
> Back to my-huge.cnf, I am sure there are many people reading the list
> who run MySQL on big-big servers, and they must have figured out how to
> optimize it. I am curious about their advice.
> 
> > > Any opinions of the following : ?
> > >
> > > [mysqld]
> > > key_buffer_size=1024M
> > > myisam_sort_buffer_size=256M
> > > sort_buffer_size=256M
> > > bulk_insert_buffer_size=64M
> > > join_buffer_size=64M
> > > max_connections=5
> > > read_buffer_size=8M
> > > read_rnd_buffer_size=8M
> > > net_buffer_length=1M
> > > max_allowed_packet=16M
> 
> Cheers,
> Gaspar

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

Reply via email to