2 options
Domino for iSeries sizing and performance tuning / IBM, International Technical Support Organization.
- Format:
- Book
- Author/Creator:
- IBM International Technical Support Organization Staff, Corporate Author.
- Series:
- IBM redbooks.
- IBM redbooks
- Language:
- English
- Subjects (All):
- Computer capacity--Planning.
- Computer capacity.
- Parallel processing (Electronic computers).
- IBM computers--Programming.
- IBM computers.
- Lotus Domino.
- Physical Description:
- xx, 502 p. : ill.
- Edition:
- 2nd ed.
- Place of Publication:
- Rochester, Minn. : IBM Corp., International Technical Support Organization, c2002.
- Language Note:
- English
- Contents:
- Front cover
- Special notices
- IBM trademarks
- Preface
- The team that wrote this edition of the Redbook
- The team that wrote the first edition of this redbook
- Special notice
- Comments welcome
- Summary of changes
- Second Edition, April 2002
- Chapter 1. Introduction
- 1.1 Conclusions and references
- Chapter 2. Overview of Lotus Domino for iSeries
- 2.1 Why use Domino for iSeries
- 2.1.1 Scalability
- 2.1.2 Reliability and availability
- 2.1.3 Integration
- 2.1.4 Proven security
- 2.2 Planning a Domino for iSeries server
- 2.2.1 Developing a Notes naming structure
- 2.2.2 Choosing the right replication topology
- 2.2.3 How security relates
- 2.2.4 What remains
- 2.3 The value of sizing, performance analysis, and tuning
- 2.3.1 Audience
- 2.4 Domino architecture
- 2.4.1 Layer 0: The kernel
- 2.4.2 Layer 1: Kernel extensions
- 2.4.3 Layer 2: System and core applications
- 2.4.4 Layer 3: Layered end-user applications
- 2.5 Tools available
- 2.5.1 Collection Services
- 2.5.2 Performance Management/400
- 2.5.3 Performance Tools (5722-PT1)
- 2.5.4 iSeries Performance Explorer (PEX)
- 2.5.5 Management Central
- 2.5.6 BEST/1
- 2.5.7 Server.Load
- 2.5.8 Performance Navigator
- 2.5.9 NotesBench
- 2.5.10 GroupSizr
- 2.5.11 WEBSizr
- 2.5.12 LoadRunner
- 2.5.13 Tivoli Manager for Domino
- 2.5.14 Tivoli Application Response Measurement (ARM)
- 2.6 NSD for OS/400 (Dump utility)
- 2.6.1 Activating the NSD tool
- Chapter 3. Sizing Domino for iSeries using the Workload Estimator
- 3.1 Introduction to Workload Estimator
- 3.2 Benchmarks to determine the load of specific workloads
- 3.3 Workload Estimator terms
- 3.3.1 Workload
- 3.3.2 Instance
- 3.4 Domino sizing concepts in the Workload Estimator
- 3.4.1 Concurrent users
- 3.4.2 Number of partitions
- 3.4.3 Clustering
- 3.5 Domino mail concepts.
- 3.5.1 Mail access types
- 3.6 Domino application concepts in Workload Estimator
- 3.6.1 Example application comparisons
- 3.6.2 Database capacity
- 3.7 Characterizing existing applications
- 3.8 Additional options for more accurate estimation
- 3.9 Using IBM Workload Estimator for iSeries results
- 3.10 Additional tips and insights
- 3.11 Consolidating Domino servers from other platforms
- 3.11.1 Capabilities of various iSeries and AS/400 models
- 3.12 Additional resources
- Chapter 4. Basic concepts of performance analysis
- 4.1 Defining a Domino for iSeries performance methodology
- 4.1.1 Relationship between Domino and the iSeries server
- 4.2 Understanding Domino on the iSeries server
- 4.2.1 Transactions in Domino
- 4.2.2 Domino base functions
- 4.2.3 Domino advanced functions
- 4.3 Domino tasks on the iSeries server
- 4.4 Application development performance
- 4.5 Lotus Domino overall performance on the iSeries server
- 4.6 The Queuing Multiplier (QM) curve
- 4.7 Dividing the CPU utilization
- 4.8 A brief discussion of threads
- 4.8.1 Threads on the iSeries server
- 4.8.2 Other Domino task that use threads
- 4.9 A brief discussion on run attributes
- 4.9.1 Run priority
- 4.9.2 How a change in run priority affects a job
- 4.9.3 Job priority considerations
- 4.9.4 Time slice parameter and tuning
- 4.9.5 How the system manages job and run priorities
- 4.10 Reviewing iSeries performance using CL commands
- 4.10.1 Work with System Status (WRKSYSSTS) command
- 4.10.2 Information about thread state transitions
- 4.10.3 Work with Active Jobs (WRKACTJOB) command
- 4.10.4 Work with System Activity (WRKSYSACT) command
- 4.10.5 Work with Disk Status (WRKDSKSTS) command
- 4.10.6 Observing network performance
- 4.10.7 Work with System Values (WRKSYSVAL) command
- 4.10.8 Display System Log (DSPLOG) command.
- 4.10.9 Start System Service Tools (STRSST) command
- 4.11 Collecting performance data
- 4.11.1 Starting Collection Services
- 4.11.2 Using Work with System Activity (WRKSYSACT) with an output file
- 4.12 Management Central performance monitor
- 4.12.1 Monitoring real-time system performance
- 4.12.2 Viewing graph history of monitor data
- 4.12.3 Exporting Graph History to PC files for analysis and printing
- 4.12.4 Combining Management Central's CPU Utilization metrics
- 4.12.5 Job monitoring
- 4.13 Reviewing data using Performance Tools/400
- 4.13.1 Print System Report (PRTSYSRPT) command
- 4.13.2 Print Component Report (PRTCPTRPT) command
- 4.13.3 Print Transaction Report (PRTTNSRPT) command
- 4.13.4 Print Activity Report (PRTACTRPT) command
- 4.13.5 Convert Performance Thread Data (CVTPFRTHD) command
- 4.14 Performance Explorer (PEX)
- 4.14.1 Add PEX Definition (ADDPEXDFN) command
- 4.14.2 Start PEX Session (STRPEX) command
- 4.14.3 End PEX Session (ENDPEX) command
- 4.14.4 Print PEX Report (PRTPEXRPT) command
- 4.14.5 Performance Explorer trace points for Domino
- 4.14.6 TPROF PEX trace
- Chapter 5. Domino logs and statistics
- 5.1 The commands
- 5.1.1 The show tasks command
- 5.1.2 Understanding the Domino statistics
- 5.1.3 Show Domino open database statistics (sh DBS)
- 5.1.4 Platform-dependent statistics
- 5.1.5 Show Domino Transactions
- 5.2 The reports
- 5.2.1 The Log database (log.nsf)
- 5.2.2 The Statistics and Reporting database (statrep.nsf)
- 5.3 Combining performance data from Domino and iSeries
- 5.4 Monitoring the Notes Remote Procedure Calls (NRPC)
- 5.4.1 Using a network sniffer
- 5.4.2 Lotus Client NRPC Monitoring Tool Client_Clock
- Chapter 6. Tuning the iSeries server for Lotus Domino
- 6.1 Tuning the iSeries server
- 6.2 Automatic performance adjustment (QPFRADJ).
- 6.2.1 The interactive iSeries tuning chart
- 6.2.2 Summary
- 6.3 Determining Domino workload
- 6.4 Choosing which memory pool to use
- 6.4.1 Using expert cache
- 6.4.2 Activity levels of memory pools
- 6.4.3 Faulting rates
- 6.5 Choosing which processor priority to use
- 6.5.1 Changing the run priority of Domino tasks
- 6.6 DASD: System ASP, user ASPs, and independent ASPs
- 6.7 Unleashing iSeries work management on Domino servers
- 6.7.1 Configuring a Domino server
- 6.7.2 Starting a Domino server
- 6.7.3 Working with Domino jobs
- 6.8 Online backup with BRMS
- 6.9 Network tuning
- 6.9.1 Maximum Transmission Unit (MTU) Size
- 6.9.2 TCP/IP buffer size
- 6.9.3 Port filtering
- 6.9.4 Duplex
- 6.9.5 TCPONLY for Ethernet
- Chapter 7. Tuning Lotus Domino for better performance on iSeries
- 7.1 Basics of Domino tuning
- 7.2 Relating Domino tasks to iSeries jobs
- 7.3 Domino parameters that affect performance
- 7.4 Domino Database indexing: Controlling the UPDATE task
- 7.4.1 Components of the Domino database indexer
- 7.4.2 UPDATE task CPU utilization in a normal environment
- 7.4.3 The UPDATE task and CPU utilization in a problem environment
- 7.4.4 Affecting the UPDATE task behavior through the view properties
- 7.4.5 Detecting UPDATE task problems
- 7.4.6 Making the changes
- 7.4.7 Conclusions
- 7.5 TCP/IP between Domino servers on the same iSeries
- 7.6 GTR search engine version 3.4
- 7.7 Using the Extended Directory Catalog
- 7.7.1 Comparing EDC to a standard directory catalog (DirCat)
- 7.7.2 Using Extended Directory Catalog to improve performance
- 7.8 Investigating mail backlogs and performance issues
- 7.9 Domino console logging
- 7.10 Number of users per Domino server
- 7.11 Using a separate partition for the R5 SMTP MTA server
- 7.12 Excessive translations on iSeries and zSeries.
- 7.12.1 Opening up any suspect job using the new Domino panel group
- 7.13 Optimizing mail: White space, compact, and quotas
- 7.13.1 Mail file size
- 7.14 Domino memory management
- 7.14.1 NSF_Buffer_Pool_Size or Nsf_Buffer_Pool_Size_mb
- 7.14.2 How queues relate to the NSF_Buffer_Pool_Size
- 7.15 Controlling the details of Domino logging
- 7.16 iSeries environment variable settings
- 7.17 Domino for iSeries specific notes.ini parameters
- 7.18 CORBA and Java servlets
- Chapter 8. Understanding the Domino server jobs
- 8.1 Domino server jobs
- 8.2 Domino server jobs (always necessary)
- 8.2.1 ADMINP: Administration process
- 8.2.2 AMGR: Agent manager
- 8.2.3 QNNINSTS: The 'Watchdog'
- 8.2.4 ROUTER: The mail router
- 8.2.5 SERVER: The main server
- 8.2.6 STATLOG: Database activity logger
- 8.2.7 UPDATE: The Indexer task
- 8.3 Domino server jobs (often used)
- 8.3.1 CLADMIN: Cluster administration process
- 8.3.2 CLDBDIR: Cluster Database Directory Manager
- 8.3.3 CLREPL: Cluster Replicator
- 8.3.4 COLLECT: Statistics collector
- 8.3.5 EVENT
- 8.3.6 HTTP: The Web server
- 8.3.7 LOGASIO: Log asynchronous I/O process
- 8.3.8 REPLICA: The replication task
- 8.3.9 SCHED: Schedule Manager
- 8.3.10 SMTP: Internet Mail Router
- 8.4 Domino server jobs (very likely not used)
- 8.4.1 BILLING
- 8.4.2 CALCONN: Calendar connector
- 8.4.3 QNNINADD: Directory synchronization add-in task
- 8.4.4 REPORT: Statistic reporter
- 8.4.5 STATS: Statistics on demand via e-mail
- 8.5 Domino server database housekeeping jobs
- 8.5.1 COMPACT
- 8.5.2 UPDALL
- 8.5.3 Fixup
- 8.6 Series SMTP: AnyMail/400 Mail Server Framework (MSF)
- 8.7 Domino server QNNxxxx programs and QSYSWRK
- Chapter 9. Integration with DB2 performance tips and techniques
- 9.1 Choosing a storage container
- 9.1.1 Domino as a storage container.
- 9.1.2 DB2 UDB as a data storage container.
- Notes:
- "SG24-5162-01."
- Includes bibliographical references (p. 477-480) and index.
- OCLC:
- 697639459
The Penn Libraries is committed to describing library materials using current, accurate, and responsible language. If you discover outdated or inaccurate language, please fill out this feedback form to report it and suggest alternative language.