Archives of the TeradataForum
Message Posted: Thu, 08 Jul 2004 @ 21:22:55 GMT
If you look at multiple data points for i/o activity (usually 10 minute collection intervals) and see if they peak and hold some value over a number of intervals, generally that means you are limited somewhere in the network (a node can move lots more than 10MbS across the backplane). And remember that in Resusage write is Teradata output, read is input to Teradata...
On the high # of blocks, if you are using ODBC have a look on the ODBC set up applet and maybe you can get better performance by upping your blocksize (65477 is the max).
And when you expect that session work is evenly distributed, but, as you show here, the data volume is quite different across nodes, you might want to take a look at how your ODBC and or host files are set up. You could have a bunch of users that resolved the host name(s) or are using a local host file and are only hitting the one NIC... Or is 205 the channel connect? You need to look at hosttype to be sure who's who...
In general, full duplex and 100MbS will give you more headroom and reduce the bottleneck potential at that point. Whether you see an increase in performance at the client depends on a bunch more things...
As always, there's a whole bunch of things to look at in this area to optimize performance...
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|