Re: Possible Threading problem with -CURRENT / MySQL?

Hi,

I will try that.

Would it be better to use 4.10 and MySQL w. LinuxThreads instead? It's
production databases that we run on the machine so stability is a must (yes
I know - 5.2 isn't stable yet...)

The reason why we decided to use 5.2-CURRENT was that the improved SMP
support - which seems to still have some bugs?

Regards
--
Lasse Laursen · VP, Hosting Technology · NetGroup Processing Aps
St. Kongensgade 40H · DK-1264 Copenhagen K, Denmark
Phone: +45 3370 1526 · Fax: +45 3313 0066

- Don't be fooled by cheap finnish imitations - BSD is the One True Code
----- Original Message ----- 
From: "Daniel Eischen" <eischen_at_vigrid.com>
To: "Lasse Laursen" <laursen_at_netgroup.dk>
Cc: <freebsd-threads_at_freebsd.org>; <freebsd-current_at_freebsd.org>
Sent: Monday, June 14, 2004 9:10 PM
Subject: Re: Possible Threading problem with -CURRENT / MySQL?


> On Mon, 14 Jun 2004, Lasse Laursen wrote:
>
> > > > WE use the SCHED_ULE, and:
> > > >
> > > > # Memory options
> > > > options         MAXDSIZ="(1536*1024*1024)"
> > > > options         MAXSSIZ="(1024*1024*1024)"
> > > > options         DFLDSIZ="(1536*1024*1024)"
> > >
> > > Try using SCHED_4BSD, then try removing all memory options.
> >
> > Wouldn't this limit us to 512 MB of memory per process running on the
> > server? we tried with each scheduler with same results. I will try to
> > recompile without the memory options and use the old scheduler. Any
hints
> > why this might work?
>
> No, just trying to see what happens with a more stock
> kernel.  Also, try removing /etc/my.conf to use default
> MySQL settings.
>
> -- 
> Dan
>
>