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
& k! r$ q1 I$ s) m9 I* Dhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
1 j' @/ r5 @+ R+ |) Z
& ^" x- r& Z$ x; q7 D; p3 sTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
% B# d( [$ ~5 ?; m+ i
2 s/ s% n) _# a; f: {! _- mLarry 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
0 s% S$ e9 L0 L0 H+ ~8 DFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
• Productivity – doing more work with less
o Improve end user productivity
6 l* Z& O1 o& bo Improves administrator productivity
9 |+ N* T+ R$ y fewer help desk calls responding to or fixing preventable problems
8 y! A/ v" h* c5 f: q1 T• Reliability
7 w- W( ]& g( c! D# h0 d( yo A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
, l' A$ P  a( p9 E+ K2 g* l( Go Fewer operational errors/problems
• Cost Savings
7 @- G+ b( n. d# @o Less waiting means less time wasted.
Quick 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.
, p" X7 m  i/ F0 o1 [" ?) NSee my March 2012 article on PLM World’s website for details:
" f/ ?( m6 T# R# }: H7 d+ z- `Teamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
, O$ R( Z# T8 U4 WCommon Performance Bottleneck Causes
, o& e4 P2 L: ?7 h. BUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded servers — Putting too much on a single server.
Operating 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.
) F3 t9 a: \+ \8 D3 H/ H6 _, ?- tDatabases – 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.
4 \% ^3 Z8 S- ~3 x. i7 N9 J+ u• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
' f* x& [: O. J$ j# w( d1 T* P• Must use dedicated DB server
4 o5 V8 z- p4 |5 e9 M: G  |2 qo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
6 i. A: g) U! A& a4 \• Must have fast dedicated storage for DB files
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
6 C3 E3 ^; E. |" `* t  wo Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
. }6 L( n  h) x' b$ l: H" Do Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
# ~5 M0 b$ t+ F/ X9 eo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
$ }8 m2 v! S" L; I0 j• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
, w9 v: M0 D  S. c• Use 64-bit OS & DB software
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.
• Use a good quality network adapter(s)
0 O9 i7 p% \2 J. D) n; c; j, ^o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
' P4 J0 `" V$ B" K5 ACommon Teamcenter Server Bottleneck Causes
7 y8 C- {  Y, \+ I* K• Overloaded Tc Servers
7 w, }, S8 m6 o- Z. z5 [  h• Poor Web Tier Configuration
• Poor FMS Configuration
1 @3 ^9 a9 J$ g1 U, c. C4 ^8 k! ^• Debugging Turned ON
• Rich Client using OOTB settings
- d0 _" O! G+ H: K‘Unload’ Overloaded Teamcenter Servers
, ]. Z  K* X' x8 S& W& G• Put Dispatcher modules on separate computers away from other Tc Servers.
7 `  Y) [% l! b; z! ~• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
! e7 W/ t; Q* p4 K8 ]" p- ^• 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.).
& j& ~% p# {& J% `9 To Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
7 |( _6 g, A% D' o* o* c+ G/ a$ B• 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.
• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
3 e+ `) }- e5 t+ x6 ~o E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
+ E: p% _: q# X* B+ MCommon FMS Bottleneck Causes
• Data improperly routed
o 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.
! a# d) w$ t4 K8 R1 |• Using OOTB settings
4 T0 P' i" ^/ T9 n7 Io For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
. Z! Y9 j. z  {) K• Not using remote cache servers for WAN users
/ p( I6 E3 ^! l' |. S* q• Not using remote volume servers for WAN users
FMS Configuration
* s- B9 m/ X, M7 X. }• Ensure routing is correct
: t  t' r" ]) Y% o7 No Between multiple FSC groups via entry/exit/link parameters
o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
2 y$ A2 [) T1 \6 v1 T& Fo Use correct transport algorithms for LAN and WAN users.
6 s) e4 u2 d$ g5 V• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
o 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
7 @2 H) i: c4 Q8 f) z# p7 g• Ensure correct client maps
  e/ M+ C. v) z0 ao 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.
/ R& Z0 f: y, f% U) ~! n! Z- m/ T• 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)
! S* i# z- u! Y) E4 a9 w: v' Zo 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.
- e& c  \0 `& \% A$ ~9 u* `% R# i& B5 x3 W• Place Volume servers close to users
* j: F9 _* D- e3 O7 L: g9 H6 V: yo Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
4 F; T2 x+ t( n% Io Greatly improve write performance (save time) over a WAN especially for CAD data.
• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
5 T, f5 ]- p5 q) i+ Jo TC_SECURITY_LOGGING=OFF
$ M  K) D. r9 A3 Y0 L5 ], s- _+ g6 Qo TC_APPLICATION_LOGGING=OFF
. a4 a8 U8 I1 G3 [- O, ~# L/ n2 ]0 ~o TC_SLOW_SQL=-1
6 V: d4 d) @. v( N# f• Rich Client ‘Teamcenter.ini’ configuration:
) y% r1 j* {! W' X. _8 ~& n, io Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
; B9 C+ Z5 [3 I( K, _: O  JNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
* j& Z0 Q  \& K( C7 }; G9 v7 v• Optimize OS network settings
- d% A& n0 s. [  M) K2 ]& io OOTB settings are insufficient
% O0 d' x  a. x! W7 O9 {# _- eo 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
Recommended Server Changes (Windows)
See Presentation.
" G4 N7 O* T! W. y  c: `6 F4 tRecommended Client Changes (Windows)
See Presentation.
6 k& d% i; M8 b. bPerformance Monitoring Tools
/ y& @- Q2 T. z! t. Z6 y" g• Some useful performance monitoring tools:
$ P* j& i, I( s1 q  X; d# b• Performance Monitor (comes with Windows)
$ [, o  i" X3 ]% L; L) u/ H• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
/ B3 S3 t# J, Y; P2 _: G3 BReference Materials
- f7 m0 ~, x4 l• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
! ]3 v. Z2 Q! Zo Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
2 x6 p+ R& `- ?* v/ Fo Teamcenter System Performance Analysis
• Oracle documentation & web sites
3 e% G+ Y! |' A6 B  r/ b• MS SQL Server documentation in addition to:
9 x! H0 L0 y+ H1 G( _9 Po Best Practices for Running Siemens Teamcenter on SQL Server
# L" `/ u8 G3 b* N http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
$ u- M; z7 T0 l5 X/ F. @o Siemens Blog on Technet
4 A' C1 f) a3 {0 j0 T http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
! A$ a5 h# i! g: b* }7 M! o http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
2 `7 N3 q( _- _% R• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
7 k* }' t8 P" [5 q- F  w+ \# \; Co JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
5 ^; D3 E, Y3 ~$ Y! WLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
; b, q8 l) j. v5 o; T& x  P/ F1 ATeamcenter 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
8 W/ O' t$ V  S+ |8 i* _9 v( L' |

xiefeixiang

调优厉害啊

a150159

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