Index_P

P

Packets Outbound Errors counter

adding to test for network errors, 494 “495

Packets Received Errors counter

adding to test for network errors, 494 “495

parallel_max_servers parameter

for Oracle system configuration and tuning, 437

Parallel-ATA (P-ATA). See P-ATA (Parallel ATA)

passivation directory

function of in EJB container tuning, 381 “382

rules of thumb for using, 382

P-ATA (Parallel ATA) vs. S-ATA (Serial ATA), 128

Pckcachesz parameter

setting in IBM DB2, 441

people redundancy

understanding, 38

percentage availability

matching with business availability, 38 “39

performance

costs associated with resolving problems with, 6 “7

as key measure of high-performance computing, 33

managing, 5 “7

operations engineering and, 2

a proven methodology for managing, 24 “30

quantifying, 1 “5

what constitutes an improvement in, 7 “8

performance analysis tools

for monitoring system load and performance status, 473 “500

performance and scalability. See performance management

performance checklist

for database-to-WebSphere implementation, 427 “428

performance improvements

business benefits of, 17

in perceived user or customer response time, 8 “9

performance management

activity phase, 506

the aim of, 25 “26

the business bottom line, 13 “14

costs for mitigating performance issues, 6 “7

example showing methodology, 505

importance of, 4 “5

key components that affect performance, 8

measurement without impact, 31 “32

the method of, 26

model for, 6

a proven methodology for, 24 “30

testing, 26

performance management tooling, 473 “500

overview of, 473 “474

performance methodology

operations methodology intersection with, 2 “3

performance monitors

time needed for analysis and review of, 18 “19

performance testing

setting your expectations, 233 “234

a WebSphere platform, 233 “251

Performance tool

importance of using the Log Report view of, 497

using for collision testing on shared networks, 494 “495

Performance tool console

main screen of, 482

performance tooling. See performance management tooling

performance tuning

decrease in operational costs associated with, 11 “13

effect of on ability to handle more users, 9 “11

importance of, 9

performance tuning checklist, 251 “287

for Windows NT, 2000, XP, and 2003, 252 “255

PerformaSure, Quest

stress and volume with application management tool, 246

persistence

issues of in multiple JVM environments, 185 “186

physical architecture. See topological architecture

physical errors

in Windows and Unix networks, 493

pilot application, 14 “17

costs associated with, 16 “17

importance of stress and volume testing in, 15

pilot phase

of the application development life cycle, 15

ping tool

testing network utilization with, 492

pipeline services

in Sun UltraSPARC processors, 100

platform costs

pre- and post-upgrade examples, 10 “11

platform derivatives

some common that WebSphere relies on, 343 “344

platform resiliency

primary goals for, 206

plus (+) button

at top of the Performance tool console, 482

Polyserv Matrix Server

as solution for applications using NFS, 349

pooled connection request

failover support for in WebSphere, 360

pooling, 27

portal

in a single-channel 3- tier topology, 178 “180

Power4 platform (IBM)

examining, 109 “115

overview, 109 “110

Power4 processor (IBM)

architecture and function of, 113 “114

vs. PowerPC 970 processor architecture, 114 “115

Power4 processors (IBM), 116

PowerPC 604e processor, 115

PowerPC 750Cxe processor

architecture and function of, 112

PowerPC 750FX processor

architecture and function of, 112

PowerPC 750 processor

architecture and function of, 111 “112

PowerPC 750 series processors, 116

PowerPC 970 processor, 116

architecture and function of, 114 “115

vs. Power4 processor architecture, 114 “115

vs. the UltraSPARC III processor, 115

PowerPC platform

selecting for your environment size , 116 “119

summary, 119 “120

PowerPC RS64-III and RS64-IV processors, 116

Preconnect method

setting in Oracle Transparent Application Failover, 369

prefer local algorithm

function of for EJB container, 335

PreparedStatement() method

using in WebSphere application design, 409

PrimaryServer directive

using to help support failover configurations, 317

process affinity

for EJB containers, 305

process semaphores

setting in Sun Solaris WebSphere-based applications, 265 “266

processor cores

function of, 113 “114

% Processor Time counter

adding for the WebSphere Java process usage, 483 “484

production environments

best CPUs and servers for large, 107 “108

best CPUs and servers for medium, 106 “107

best CPUs and servers for small, 105 “106

most simplistic WebSphere topology for, 174 “178

selecting the right CPU for a large, 118

selecting the right CPU for a medium, 117 “118

selecting the right CPU for a small, 117

selecting the right CPU for large Power4-based, 118

profiling

a practical approach to, 505 “507

profiling and benchmarking

applications running under WebSphere, 503 “517

to isolate where problems are occurring, 504 “505

key points that should make up your approach, 507

revisited, 503

tools available, 507 “517

profiling and load testing applications

for WebSphere application environments, 243 “244

proprietary clustering (software clustering)

function of, 293 “294

ps command. See Unix ps command

Purge Entire Pool option

in Purge Policy in WebSphere 5, 450 “451

Purge Failing Connection Only option

in Purge Policy in WebSphere 5, 450 “451

Purge Policy

setting in JDBC connection pool manager, 444

setting in WebSphere 5, 449 “451