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
8 k- i/ g8 C! v' J- Hhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

" {$ A; s% O& J( A/ Y! [Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
7 a$ p  j/ g. |  j5 X! _
Larry Carpenter
3 E7 n# |. V# {& O. O4 Y/ a; o3 }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
" G; B# L" v: I% c* iFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
7 x, p5 |  @. nWhy Performance Matters
+ W+ x# R: L) j# v! S6 p$ C5 `! o• Productivity – doing more work with less
% e$ A' `0 O7 s- a8 d* }o Improve end user productivity
o Improves administrator productivity
4 m! Y. s, g' I, s' h fewer help desk calls responding to or fixing preventable problems
• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
4 t' |& H8 O- Y* l) p+ F4 uo Less opportunity for data corruption
o Fewer operational errors/problems
! ~% U2 c  V- Q/ c8 g. U• Cost Savings
o Less waiting means less time wasted.
% E2 y: {- ?2 _+ Z% Z6 _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.
) g5 O; J8 \; Y9 ?1 e6 q2 PSee my March 2012 article on PLM World’s website for details:
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.
% t" ?  p2 a) V& a  K$ HOverloaded servers — Putting too much on a single server.
; p+ b) ~* P  FOperating system settings — Network settings most common (e.g. TCP parameters).
3 g5 J, M+ f1 X, f: P( l7 x/ s0 lLack 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
& L- Q" S0 D" q$ i9 y9 W) H• Database performance is highly sensitive to hardware, software, and DB configuration.
2 c- ]% n4 H; M/ Z  t9 d* _; C• 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.
Mitigating Database Server Bottlenecks
• 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.
• Must have fast dedicated storage for DB files
& j. _" P; M/ A; i8 m$ Y! ?( Ao Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
$ x8 g8 P' b+ do Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
2 z+ O& a! f+ |' d& x7 ?: Z3 o. T) `o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
$ [. I1 \' `9 j; m+ z/ So Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
+ ^% l! r; ~7 U% n• Use 64-bit OS & DB software
. z! q- W, C: [% U1 z- i* f( Bo 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.
5 Q3 X# v, E, L" c• Use a good quality network adapter(s)
+ _1 u- N! @3 r0 Do Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
" {, o- R/ u0 b$ Co Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
6 a; |. ~0 T' h0 }  l1 l  k• Poor Web Tier Configuration
• Poor FMS Configuration
- r$ Z# j; }! ]" E• Debugging Turned ON
• Rich Client using OOTB settings
, ?1 f. l4 F* e: k+ k. L0 e‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
4 \& D* W" @6 }& R  S• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
/ p$ V7 r- d' |7 P3 r  g( A# u) c• Use load balancing for Middle Tier & FMS:
8 N! [9 ?0 U9 O; b7 K& X' g- m/ g* jo 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.).
5 F6 |5 r9 h" g7 o1 O& b3 M; So Set up multiple FSC cache servers to take load off busy volume servers/storage.
4 Z" w. l: b% b* S" rWeb 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.
% G8 |# @  h% n+ a• Enable http compression if not using WAN acceleration
4 I, |3 P3 r1 xo Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
: n; N0 r# |# m4 B( ko E.g. timeout values, max # of threads, Java memory, etc.
: i$ I/ a$ J6 \4 z7 P# ]+ x' mo Read tuning guides specific to your chosen web server/app
; O+ s7 A' W  x. O" T• Scale it up or sideways
5 b/ D! y' p$ u* S" {" R" Z6 t6 so Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
1 i: b( F3 |7 ^; ]7 Q( x: VCommon FMS Bottleneck Causes
/ I- b$ L! E0 f4 R• 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.
' m7 x9 H" ?% d$ t+ B• Using OOTB settings
" P5 _6 ?4 b. e. H7 L' Ao For development purposes only, remember?
0 K( U! v' y8 O$ i• Missing client IP address subnets
• No load balancing
3 a& E, b5 A- x- y• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
o 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.
$ n5 l% X" U5 B; `" wo Use correct transport algorithms for LAN and WAN users.
  j; h$ |  X1 j/ `) B' j( C• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
, i# ~, L7 \# Go 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
• Ensure correct client maps
  Y  h/ x$ @1 Io Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
. ^; w% f# @9 K, Y, d+ Z4 T6 h3 w$ ro Place client maps in the closest FSC group to their location.
1 ~8 X/ E0 W& ^4 d• Use multiple FSCs for load balancing
  [5 }/ K' i2 e  A$ `6 m* No Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
o 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.
) ^: \% [- a* X0 v  `/ y9 c• Place Volume servers close to users
5 M! }+ |* l! I0 c6 F; r( D0 {o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
7 _% j( [, `, v1 g. M+ P4 i+ co Greatly improve write performance (save time) over a WAN especially for CAD data.
0 v. ?8 a* V% N# i6 f4 E9 R• Prepopulate FSC caches
4 Z' L" {* e9 C7 i7 Oo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
1 B- _) {  d# I/ x3 v* G' b7 k8 g6 S• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
  c5 U: F1 f( T! x/ v  z: E5 `8 fo TC_SLOW_SQL=-1
' G/ X+ M) y4 m2 P7 h1 H9 @3 E( n• Rich Client ‘Teamcenter.ini’ configuration:
7 }- A. A2 s  B% b2 @) lo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
4 y& i$ k4 h' B2 }) {( O$ R" a• Enable FCC File Warming
" Y( @9 s: I4 F  M8 p" d5 P5 to Improve startup time by having FCC and Tc files pre-loaded at OS login.
/ ~' l" U3 i! R  uNetwork 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)
• Optimize OS network settings
o OOTB settings are insufficient
/ H! Y. ^# a" r1 q- ?7 A, `o Applies to both servers and clients
* w; C. T& b: o; Y$ q3 ]8 Xo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
& K2 I& v& O6 `% D7 ORecommended Server Changes (Windows)
/ x2 @; a5 t* R. ^1 a8 w& V0 Y9 QSee Presentation.
Recommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
4 R$ U) y* d" j6 ]0 w3 I" |• Performance Monitor (comes with Windows)
) P/ a8 ^! Z2 e; n) r4 _- O3 ^3 E• Used to monitor OS, Teamcenter, and SQL use of resources
* l# d' {/ M% D, @( B• Wireshark (freeware network packet sniffer)
9 R& s! [' O5 D* _• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
8 L$ T6 n2 V& \: b$ y+ E9 q• Sysinternals Suite (free from Microsoft web site)
" T- B( p, y8 p1 b• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
+ I7 E# @3 I. R  bo Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
2 b: j4 ~$ \6 \3 L% l& to JBoss 4.2.2 Installation & Tuning Guide
. m' ?- y" Q' N/ P! Qo Optimizing Teamcenter Client Performance
( ?1 F  |+ o. m" \o Teamcenter System Performance Analysis
• Oracle documentation & web sites
7 \. L- {: ~7 L8 g: y& y, Z• 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
o Siemens Blog on Technet
3 J  D& ^6 Y- M" A http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
 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
3 J6 P- n$ r$ i4 c3 io Teamcenter – Database Performance
- k8 V  a+ ?; R# L& V3 ho JBoss Optimization for Teamcenter
$ z- v9 |2 p1 V  V4 J2 Go Optimizing Teamcenter Client Performance
( O! A& M; b5 M5 i9 B5 Jo Teamcenter Database Server Configuration & Tuning
1 U. z6 [2 A' g  Y. W  @Contact Information
: s! \3 ]- b: E! F+ cLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
5 o+ c* I- a5 M6 h/ [$ |LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
; ]4 t5 p& o% y9 p8 D1 UAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

xiefeixiang

调优厉害啊

a150159

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