We are just migrating our instances to TSM 6.2.2.0 (from 5.5.4.2). Our limited experience shows us that DB2/TSM6 is hammering our CPU (mostly in db2sysc processes). As Roger suggests, we did not ignore DB i/o bandwidth either, but I am surprised at how much CPU it seems to want. We have 7 instances (5 active) on 8 (p6) cores, and our CPU is currently pegged most of the day. I don't know yet whether this is "expected/normal", or whether we still have some reconfiguring/patching to do to address this.
..Paul At 01:35 AM 1/12/2011, you wrote: >I'd be more worried about database I/O bandwidth. Expiration and >deduplication are going to hammer the database. All the usual rules >apply, such as avoiding RAID5, using your fastest disks, using striping, >not overloading any one bus, controller, or drive. If you have any of >these bottlenecks then adding more cores cannot improve performance. >Poor database disk I/O can kill a TSM system, regardless of its CPU >resources. If you've got the budget for it, think about using solid >state storage for the TSM database in order to support multiple >expiration and deduplication processes. > >Roger Deschner University of Illinois at Chicago rog...@uic.edu >"Fine, Java MIGHT be a good example of what a programming language >should be like. But Java applications are good examples of what >applications SHOULDN'T be like." >- pixadel > > >On Tue, 11 Jan 2011, Schneider, Jim wrote: > >>Good morning, TSM fans! >> >>I'm building an AIX 6 TL4 server to run TSM Server 6.2.2.0. The >>Performance Tuning manual tells me I need one core per expiration or >>deduplication process. How many processors are you folks using, and >>does additional processing power have a significant benefit? >> >>Thanks in advance, >>Jim Schneider >> -- Paul Zarnowski Ph: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801 Em: p...@cornell.edu
