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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
/ ^2 f$ y9 Q: V: k1 g2 Ihttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
1 x; c$ D  i: [
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
3 J% p+ ~  s) O( K
9 j% @6 K+ g- ^5 q! XLarry 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:
Why Performance Matters
• Productivity – doing more work with less
0 L" ]- \/ S+ \: N$ D, A. ~o Improve end user productivity
o Improves administrator productivity
0 s9 g& k0 e& }" i4 b; x- c fewer help desk calls responding to or fixing preventable problems
* Q5 L( c; c) X& i# @% [* x• Reliability
+ q. S+ J* s, M( z$ z- t* _' Do A well tuned Teamcenter environment also improves system stability and uptime.
* P' n% |2 U: D1 Do Less opportunity for data corruption
o Fewer operational errors/problems
, q7 e0 u9 N8 ?9 O- z8 u% J, U1 h• Cost Savings
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.
4 ~" F- \9 G. H8 _See my March 2012 article on PLM World’s website for details:
2 Y& U  [# t: H) `8 J! I/ uTeamcenter 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.
# s& w5 n; F# R5 E5 f/ s% p: aOverloaded servers — Putting too much on a single server.
; d4 z$ N% P! LOperating system settings — Network settings most common (e.g. TCP parameters).
9 V7 P# d" C, w" D% ~! _  _Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
% ~& k# D6 T0 W+ n! e/ {Databases – The Most Likely Culprit
" I) @( N1 f( Y3 ~. W• Database performance is highly sensitive to hardware, software, and DB configuration.
7 m4 H% y3 P, w* G; w• 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
# v# G9 S: p. e2 k* g4 _) Ko Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
: j# K4 N0 h2 {: @) z• Must have fast dedicated storage for DB files
, D% |$ z% X, [o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
) D' ~' m( e" s8 I, z; D, J$ eo 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.
/ `8 `: v: v; T9 yo Use disk controllers with a battery/flash backed cache.
7 O  z. K4 Z6 g. R* }$ Yo Use multiple disk controllers if possible.
. W( I5 A; X' w9 g• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• 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)
3 k1 T* f) _4 c6 _, g& g; yo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
• DB maintenance tasks
% s- W6 u+ H1 R: H: {o Update statistics and rebuild indexes regularly.
0 u: ^5 \- `9 D# D4 A: U5 jCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
• Poor Web Tier Configuration
3 K. T" `' Z" P/ @8 a( F; w! }. F• Poor FMS Configuration
• Debugging Turned ON
/ L; P' ~* c" P• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
) R- C( |- |; U) c) J• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
4 X6 A" [5 e, B8 c1 D" zo 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.
8 @; t7 V6 H. x+ q8 fWeb Tier Configuration
• Do not use port 80 or 8080
  D" ?9 C6 {" L" I' {1 Do 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.
0 s, j$ n2 |( ^$ w+ Y8 u7 t, W" |• 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
o E.g. timeout values, max # of threads, Java memory, etc.
- z9 Q" |( B: Wo Read tuning guides specific to your chosen web server/app
6 w+ y1 v1 _& y  [• Scale it up or sideways
2 f2 c9 E; |% d# ~* K8 E  {/ uo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
) [0 n- T% f" [: }+ u$ x• 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.
* W. L" V& s( K: D: p• Using OOTB settings
, O$ g. O) y/ F' q4 I8 ao For development purposes only, remember?
• Missing client IP address subnets
& Q; R& {% [. g7 `5 x+ {; _• No load balancing
, C& J$ ~+ L' J; j! x+ A) r• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
6 i+ ?* c8 i( ]! v. lFMS Configuration
/ C; M) m( I) T. i• Ensure routing is correct
; q& E! y$ e. V8 V$ Q, v/ A$ C8 go Between multiple FSC groups via entry/exit/link parameters
3 |9 H$ f3 k. I% E' v, w0 B1 A. mo Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
o Use correct transport algorithms for LAN and WAN users.
% I# q( ^" q) y9 n; _) Z• 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
9 N: F( m: l# u/ c: f4 `• Ensure correct client maps
+ E7 Z3 J6 L; z/ }! }/ _. Po 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.
4 u3 ?' P4 d; E9 F• 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)
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.
8 l% D, I' x8 E' F# L• 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)
/ m1 I+ x/ E$ |& ^: do Greatly improve write performance (save time) over a WAN especially for CAD data.
" r# l+ y6 X: m4 H• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
& n) N' f' t( ^• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
% A1 J1 |: w- t1 ~. I7 m; l, ho 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).
- b: t9 z  ~& Z• Enable FCC File Warming
( t& w5 b! H/ T7 V/ w+ j/ io Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
1 U; L! _9 n& s( J  [$ g( h) E* u% M• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
4 h2 e6 |, K; @: S( Eo If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
: ]' w: Q+ i2 s$ {• Optimize OS network settings
* ?) H# _3 T5 C8 \4 jo OOTB settings are insufficient
- H# X6 t  D/ mo Applies to both servers and clients
! B5 K# [1 c: n6 b/ V2 i/ oo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
' y, g5 q" {+ w% _& ?Recommended Server Changes (Windows)
See Presentation.
( H: m) T2 s  E$ K& ~8 g# URecommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
3 V) `3 q9 R7 s3 W( ?4 F* i• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
5 S$ z# ?# h/ r& ^6 l6 |• Used to monitor OS, Teamcenter, and SQL use of resources
( y& J2 ^; t; A• Wireshark (freeware network packet sniffer)
% A) Q" G8 s1 G3 C# O; s• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
- C$ H2 N% m% o5 f: X• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
3 G+ a* R& A+ Y/ Xo Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
/ ?9 }3 g- _7 q8 `o Teamcenter System Performance Analysis
  K) d+ D$ R5 k9 H/ i4 [; {1 u• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
# M$ ]- D' T  x8 i' do 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
, c& p$ j5 ^( v1 H+ I) b' b1 Go Siemens Blog on Technet
) c& r2 H+ j  `& Y% e- s; } http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
& ~0 \% D2 t* J0 l" U& Ko Siemens-Teamcenter-SQL-Resource-Page
9 ]+ y) T7 Z( O7 R) [8 ` 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
! [# {4 G2 Z/ ?+ m5 e' b) Lo Teamcenter – Database Performance
0 ~$ S* X% U. L4 n3 A1 |+ Co JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
* E: d! ^$ a2 _Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
' w3 }# n" U+ s9 ?; B4 l
7 n2 P3 G, G  l

xiefeixiang

调优厉害啊

a150159

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