OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Load Balancing with MAXCPU exhibits different locking behavior

From: Robert Klemme (shortcuttergooglemail.com)
Date: Thu Sep 15 2005 - 09:37:09 CDT

Thanks for the hint. I'm still interested in an explanation what
really happens here. Any takers? Thanks!

Btw, the test with MAXCPU=2 also exibits similar behavior: four bulk
loads started in parallel, only two active import tasks and they seem
to hang. Also there are numerous lock collisions (~350 at the
moment). There also seem to be only two processes loadercli although
four were started concurrently (via dbmcli) and there is no message of
termination yet. When the process finally terminates I'll post error
messages.

Kind regards

robert

2005/9/15, danteamcmi.com <danteamcmi.com>:
> Robert,
>
> Try MAXCPU=2. A hyperthreaded processor does not count as two processors. The
> MAXCPU setting is set to the number of processing cores, e.g. dual processor=2,
> dual core=2.
>
> Good Luck,
>
> Dan
>
> Quoting Robert Klemme <shortcuttergooglemail.com>:
>
> > Hi all,
> >
> > we did some tests with different settings of MAXCPU (1 and 4) on a
> > dual processor board with hyper threading. MaxDB version is 7.5.00.18
> > on Windows. For each test we started 4 bulk loads concurrently into
> > the same table. With MAXCPU=1 there were no problems and bulk loads
> > completed normally. With MAXCPU=4 the database run into a lock
> > collisions and all imports hang.
> >
> > Is this expected behavior? What bugs me is that even with MAXCPU=1
> > all four bulk loads run in parallel so at least from the observer's
> > point of view nothing changes. This would be different if only one
> > bulk load would be running at a time.
> >
> > Did I miss something? Is this a bug? Thanks!
> >
> > Kind regards
> >
> > robert
> >
> > PS: I searched the bud database but did not find a single entry that
> > contains "MAXCPU".
> >
> > --
> > MaxDB Discussion Mailing List
> > For list archives: http://lists.mysql.com/maxdb
> > To unsubscribe: http://lists.mysql.com/maxdb?unsub=danteamcmi.com
> >
> >
>
>
>
>
> ----------------------------------------------------------------------
> This mail sent through Horde-Toaster (http://qmailtoaster.clikka.com/)
>
> --
> MaxDB Discussion Mailing List
> For list archives: http://lists.mysql.com/maxdb
> To unsubscribe: http://lists.mysql.com/maxdb?unsub=shortcuttergooglemail.com
>
>

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb