EEE coordinator partition/node

Dave Shapiro

EEE coordinator partition/node
Hello List,

How are you folks that are using UDB EEE for warehousing configuring your coordinator partition/node for performance?

We currently use Node 0 as the catalog and default coordinating node. Node 1 is the first "data" node. One of the performance Redbooks makes a reference to this configuration purposely for performance i.e. more CPU is available on Node 0 for being the coordinator node.

We have also seen a recommendation that the default coordinator node NOT be the catalog node, but instead be the first data node. This would be accomplished by setting the current node to say 99 when the database is first created. This makes the catalog node 99, but the default coordinator node is still node 0, which is now a "data" node.

What if there were only two nodes in the database, one catalog node 0 and one data node 1?

Any hints and tips would be greatly appreciated!

TIA

Dave

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Smit

Re: EEE coordinator partition/node
(in response to Dave Shapiro)
Dave,

I'am not an EEE expert but as far as I know:
- node 0 -> catalog node
- node 1..X -> data nodes
- you can connect to all nodes and if you know that for one application most
of
the data is in node X then it is better to connect to that node....with
that application.
- V8 brings a catalog cach so the time to get catalog info wil speed up....

But as I said I'am not an EEE expert.....perhaps someone
can give you more info or can tell you that I'am wrong :-)

Greetings,

Robert E. Smit
ZeluS Support

----- Original Message -----
From: "Shapiro, Dave" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Sunday, December 21, 2003 10:28 PM
Subject: EEE coordinator partition/node


Hello List,

How are you folks that are using UDB EEE for warehousing configuring your
coordinator partition/node for performance?

We currently use Node 0 as the catalog and default coordinating node. Node
1 is the first "data" node. One of the performance Redbooks makes a
reference to this configuration purposely for performance i.e. more CPU is
available on Node 0 for being the coordinator node.

We have also seen a recommendation that the default coordinator node NOT be
the catalog node, but instead be the first data node. This would be
accomplished by setting the current node to say 99 when the database is
first created. This makes the catalog node 99, but the default coordinator
node is still node 0, which is now a "data" node.

What if there were only two nodes in the database, one catalog node 0 and
one data node 1?

Any hints and tips would be greatly appreciated!

TIA

Dave

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Barry Noble

Re: EEE coordinator partition/node
(in response to Smit)
In our environment we have 5 nodes with node 1 being our catalog node and it
also has the smaller tables that I'll call edit and code tables. This node
is also our coordinator node for queries. The other 4 nodes are for the
larger tables and we have them split across the 4 nodes. This was done on a
recomendation by IBM at the time we built this EEE database.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Smit
Sent: Monday, December 22, 2003 7:49 PM
To: [login to unmask email]
Subject: Re: EEE coordinator partition/node


Dave,

I'am not an EEE expert but as far as I know:
- node 0 -> catalog node
- node 1..X -> data nodes
- you can connect to all nodes and if you know that for one application most
of
the data is in node X then it is better to connect to that node....with
that application.
- V8 brings a catalog cach so the time to get catalog info wil speed up....

But as I said I'am not an EEE expert.....perhaps someone
can give you more info or can tell you that I'am wrong :-)

Greetings,

Robert E. Smit
ZeluS Support

----- Original Message -----
From: "Shapiro, Dave" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Sunday, December 21, 2003 10:28 PM
Subject: EEE coordinator partition/node


Hello List,

How are you folks that are using UDB EEE for warehousing configuring your
coordinator partition/node for performance?

We currently use Node 0 as the catalog and default coordinating node. Node
1 is the first "data" node. One of the performance Redbooks makes a
reference to this configuration purposely for performance i.e. more CPU is
available on Node 0 for being the coordinator node.

We have also seen a recommendation that the default coordinator node NOT be
the catalog node, but instead be the first data node. This would be
accomplished by setting the current node to say 99 when the database is
first created. This makes the catalog node 99, but the default coordinator
node is still node 0, which is now a "data" node.

What if there were only two nodes in the database, one catalog node 0 and
one data node 1?

Any hints and tips would be greatly appreciated!

TIA

Dave

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Dave Shapiro

Re: EEE coordinator partition/node
(in response to Barry Noble)
Thanks for the feedback Barry!

Any one else doing anything different?

Dave Shapiro
IT System Analyst-Sr, S5-S60
Information Services
(515) 235-1242


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of barry1
Sent: Tuesday, December 23, 2003 4:07 AM
To: [login to unmask email]
Subject: Re: EEE coordinator partition/node


In our environment we have 5 nodes with node 1 being our catalog node and it
also has the smaller tables that I'll call edit and code tables. This node
is also our coordinator node for queries. The other 4 nodes are for the
larger tables and we have them split across the 4 nodes. This was done on a
recomendation by IBM at the time we built this EEE database.

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Smit
Sent: Monday, December 22, 2003 7:49 PM
To: [login to unmask email]
Subject: Re: EEE coordinator partition/node


Dave,

I'am not an EEE expert but as far as I know:
- node 0 -> catalog node
- node 1..X -> data nodes
- you can connect to all nodes and if you know that for one application most
of
the data is in node X then it is better to connect to that node....with
that application.
- V8 brings a catalog cach so the time to get catalog info wil speed up....

But as I said I'am not an EEE expert.....perhaps someone
can give you more info or can tell you that I'am wrong :-)

Greetings,

Robert E. Smit
ZeluS Support

----- Original Message -----
From: "Shapiro, Dave" <[login to unmask email]>
Newsgroups: bit.listserv.db2-l
To: <[login to unmask email]>
Sent: Sunday, December 21, 2003 10:28 PM
Subject: EEE coordinator partition/node


Hello List,

How are you folks that are using UDB EEE for warehousing configuring your
coordinator partition/node for performance?

We currently use Node 0 as the catalog and default coordinating node. Node
1 is the first "data" node. One of the performance Redbooks makes a
reference to this configuration purposely for performance i.e. more CPU is
available on Node 0 for being the coordinator node.

We have also seen a recommendation that the default coordinator node NOT be
the catalog node, but instead be the first data node. This would be
accomplished by setting the current node to say 99 when the database is
first created. This makes the catalog node 99, but the default coordinator
node is still node 0, which is now a "data" node.

What if there were only two nodes in the database, one catalog node 0 and
one data node 1?

Any hints and tips would be greatly appreciated!

TIA

Dave

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm