138. 解决teamcenter性能差的建议----值得学习!!!!

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
4 b) R4 W9 w7 D! Q. M+ @
/ b( |* w8 U  `: MTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
0 ^& m! s  A: }
! ^0 h. C8 V0 E& X2 v, k/ f3 \9 bLarry Carpenter
At the Chicago-Wisconsin RUG Fall Conference in October 2012, I gave a presentation on common Teamcenter performance issues and solutions along with listing, in one place, many other past Teamcenter performance presentations and white papers. It was very well received by a standing room crowd, so I thought I'd share it with the rest of the PLM World community. Here is a link to the presentation (you must be a TCUA SIG member to view it):  http://www.plmworld.org/p/do/sd/sid=3758&type=0
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
. \( j# [0 L/ e2 p5 NWhy Performance Matters
! B# K3 P7 _  D5 S8 D% x• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
9 _; G: H' Q' F! b( U2 l# U: f• Reliability
, {+ e$ y3 Y4 z$ \1 Eo A well tuned Teamcenter environment also improves system stability and uptime.
) p: S% j! O# M6 Q( h  Jo Less opportunity for data corruption
5 ], g& d3 {+ h+ Z% Po Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
0 V! m1 \* p# d7 h0 rQuick Case Study: Company ‘S’
Performance was so bad that something which used to take 10 minutes was taking 2 hours to do.Did pretty much everything wrong, performance-wise, at first but ultimately fixed every major problem. What took 2 hours now only takes 2 minutes.
9 \8 ~: A  R: s2 XSee my March 2012 article on PLM World’s website for details:
* c- \$ s( j5 u6 p# l1 H( ~/ |Teamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
; x8 r8 Z1 W- _Overloaded servers — Putting too much on a single server.
! K6 O  m% w! mOperating system settings — Network settings most common (e.g. TCP parameters).
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
Databases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
0 d7 t/ v; l# l  I6 F' XMitigating Database Server Bottlenecks
5 Q& Z6 S! h/ x3 d• Must use dedicated DB server
o Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
3 O$ X) h' \% o4 c7 J• Must have fast dedicated storage for DB files
; ~' }/ ~# I+ v# bo Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
o Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
$ q" X, O8 P; H" Z2 ^+ [/ J# oo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
• Cram the RAM
/ w( v/ K: C' j2 c' S  do Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
& ^2 i0 W0 e% b• Use 64-bit OS & DB software
7 m& S9 U, ?2 p: @8 ?o 32-bit software has severe limitations regardless of whether you use “/3G”, AWE, or PAE settings to access memory beyond 3-4G. It’s still a bottleneck.
; u0 P$ R& b8 P4 n2 f• Use a good quality network adapter(s)
o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
( N5 s1 T  j1 Yo Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
# [5 r  b; m/ v7 n7 A3 Y/ t• Overloaded Tc Servers
• Poor Web Tier Configuration
* t7 F* G; Y/ f• Poor FMS Configuration
; `  L: `! e: o& P% W5 E• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
* T9 y& e# X( K) f• Put Dispatcher modules on separate computers away from other Tc Servers.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
o Use multiple Web/Enterprise Tier servers to open up potential hardware resource bottlenecks (e.g. CPU, RAM, network adapter I/O, disk I/O, MB bus, etc.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
9 F5 x  c' B% `/ X# C* C! ^Web Tier Configuration
• Do not use port 80 or 8080
o HTTP traffic on those ports is considered web browsing traffic and is therefore given lowest priority on any network. Can also cause randomly dropped connections.
5 f; V! ?( h& @& P' L0 o4 q% h• Enable http compression if not using WAN acceleration
$ U' Y, L# a- O3 Po Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
! M8 f$ D) @, U, t/ u, uo E.g. timeout values, max # of threads, Java memory, etc.
9 {1 e  c4 o) x2 to Read tuning guides specific to your chosen web server/app
) p0 K! r& R$ L' t0 o; X8 r; [4 i' V• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
% h' U9 Z# u& B/ \$ J" V7 l3 FCommon FMS Bottleneck Causes
• Data improperly routed
  R- T# W6 t3 v- z, ]! l, |, jo E.g. Forcing data to go through a remote FSC server over a WAN and back again over the same WAN instead of simply pulling it directly from a nearby Volume/cache server.
9 U0 S* Y( d1 u5 l: S1 g3 _• Using OOTB settings
- m: v. q$ k- h6 E# i# e4 Y4 b  uo For development purposes only, remember?
• Missing client IP address subnets
' {3 B7 n1 b' ?$ n5 |• No load balancing
• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
3 j( B, J6 L9 d  O7 vFMS Configuration
  m8 ?: Q, Z& B& S2 L+ `5 j  y( c9 n• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
" K5 |( i8 S$ `* A* A# |o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
' p/ M5 B1 w0 t7 S) {o Use correct transport algorithms for LAN and WAN users.
3 g& q7 M* W0 |8 r• Tune FSC/FCC cache settings
8 J7 o1 m4 A4 yo Simply picking a total read/write cache size is not enough.
- q& Y8 l# C! E2 vo Read “Sizing the FMS fast cache” in the Teamcenter help documentation. There is also a FMS cache sizing tool available from the GTAC web site. Link to FMS Calculator
4 k, H( f  D9 z; `• Ensure correct client maps
o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
o Place client maps in the closest FSC group to their location.
% h% L1 {' L. B# {5 ^4 n8 }• Use multiple FSCs for load balancing
o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
! U% k# v3 }1 k- G6 y: e. fo Use redundant FSC cache servers to load balance each other. Also provides fail-over.
• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
1 y1 J( L4 D( z$ |& ?% Ko Greatly improve write performance (save time) over a WAN especially for CAD data.
1 z  m6 A' [4 B1 f0 a• Prepopulate FSC caches
8 V8 E* t( d( H9 V/ xo Run a nightly script to prepopulate shared data across FSC caches.
1 K6 K  s% _- s" {6 ?$ R5 L0 oMisc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
' H. g# o# u( Z& J0 ?6 w% Go TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
o Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
/ S- H/ J: p; _2 L. @• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
) K/ _. Y! N7 H- p: l• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
. n; Q: n5 b4 ]4 A% Z* Y4 y, So If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
' v" k! c6 l; b- o, P• Optimize OS network settings
o OOTB settings are insufficient
. w- l+ m+ A3 D' co Applies to both servers and clients
o Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
5 f- x; r. F2 D7 CRecommended Server Changes (Windows)
" _& z8 B: p, z  |See Presentation.
0 }5 x9 |' f% i$ P& aRecommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
. p3 i, r, m; ~, s" `6 x7 p$ v• Some useful performance monitoring tools:
7 n7 p% o$ D- u+ \$ e" F• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
. r/ {. F4 ~) s" D$ A• Available at http://www.wireshark.org/
  N$ i. z! V, ]• Sysinternals Suite (free from Microsoft web site)
2 ^0 \' R+ Q5 N6 L• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
0 l7 l8 f! \. ^0 I3 d• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
# P! K- ^( q. ~$ O4 t- _o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
, }$ u3 j' S+ e# M  f7 T3 jo JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
o Best Practices for Running Siemens Teamcenter on SQL Server
 http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
) V  L) x1 c: I: {* s; N0 yo Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
2 B6 o, T9 e' l4 T http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
0 B3 ?" @4 R8 m7 r+ g. q5 i8 {, Ho JBoss Optimization for Teamcenter
' a+ ^4 F' F2 }/ H3 Vo Optimizing Teamcenter Client Performance
( Y8 d& e- a& w, C6 I' co Teamcenter Database Server Configuration & Tuning
Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
$ s! m( X. N; Y1 {' o& M/ ZTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

xiefeixiang

调优厉害啊

a150159

总结全面，我们也是类似情况，找了西门子的团队过来优化的