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
1 p2 ?% Q! l; _. n6 D" m! Bhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
  b" N5 v! `1 W0 g9 T! e/ |
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
! i, Q  A9 x9 u$ l$ W9 S; T- {1 V
2 W5 G: P6 ~8 MLarry Carpenter
/ m9 H: \# z& |! V# w0 |) J, yAt 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:
" o5 X+ Q7 I$ Q: S7 p; M) u! P4 i, Y+ qWhy Performance Matters
• Productivity – doing more work with less
o Improve end user productivity
) H7 b1 F6 E4 r/ a7 mo Improves administrator productivity
* O8 {# N% d  H0 F$ Q6 R fewer help desk calls responding to or fixing preventable problems
0 P% _' E2 L# o- r' N• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
$ e( t( u+ J0 l2 g7 g" wo Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
7 F. ]9 L: d! @' D& Y: g% G, mPerformance 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.
See 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
" Q% u7 ]$ n; r* Y8 fCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
1 C2 \: l( e+ K6 S; U1 v8 sOverloaded servers — Putting too much on a single server.
  k, q* h- `5 B* s' x! y* a5 KOperating system settings — Network settings most common (e.g. TCP parameters).
0 K9 S4 e8 Y6 z6 l( o* x, gLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
5 f5 y  ^& Y- ]" H9 d' tDatabases – The Most Likely Culprit
4 w5 N: v: A+ R; `2 S; w• 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.
Mitigating Database Server Bottlenecks
• Must use dedicated DB server
7 {/ J( D$ F0 T$ z- {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
* p  D, G5 N$ f0 no 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.
1 X+ g7 s3 ?' ]) R. u- lo Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
) e9 }' R+ O, `# ro Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
5 l; }* D* q8 L3 ]9 F• Cram the RAM
7 p# T% L& ]2 ~" j! do Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
4 T  T) r* Z6 D+ e8 D/ n: T/ G! h8 b, d• Use 64-bit OS & DB software
* b# `+ x# b4 E1 B! h) U0 Yo 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.
& L( ?% t1 F; ^0 P3 t• 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
o Update statistics and rebuild indexes regularly.
0 @# k, H9 M: K' R9 SCommon Teamcenter Server Bottleneck Causes
9 o0 \0 \* M0 x) ~! v; [0 @! X• Overloaded Tc Servers
% q& l7 a5 T+ Z• Poor Web Tier Configuration
4 ?% N! w# i; c• Poor FMS Configuration
• Debugging Turned ON
6 n# a& \& }' z3 \- g• Rich Client using OOTB settings
# d/ o& H. u9 f. o. U, N: C0 v; \* B‘Unload’ Overloaded Teamcenter Servers
! ~9 i# p% N& R) n4 i2 L- Z• Put Dispatcher modules on separate computers away from other Tc Servers.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
$ v2 H7 u* ]: G7 U7 S. w/ t• Use load balancing for Middle Tier & FMS:
1 o- `5 S) a' {' fo 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.).
4 |5 b) U" s( E( m0 _- zo Set up multiple FSC cache servers to take load off busy volume servers/storage.
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.
• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
- \5 M# g% G/ X6 V* p# U, d• Change/tune OOTB settings for Web Server/App
o E.g. timeout values, max # of threads, Java memory, etc.
# g6 F* h- D4 K" g  K6 ?  Fo Read tuning guides specific to your chosen web server/app
! N, N+ @/ n0 Z0 a7 }5 C0 c• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
0 ]1 L- @8 w- [' x* G, k• 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.
• Using OOTB settings
. U" W" X% s! ~o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
, \, c1 `7 a7 m! ~, f• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
' }' }$ b2 k* T: }, u9 Y, `2 [1 e• Ensure routing is correct
2 J/ h+ j! r0 l' bo Between multiple FSC groups via entry/exit/link parameters
% T0 x8 m& U1 i: [o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
& O! A$ \# |9 j- m& j* V6 u/ E1 {o Use correct transport algorithms for LAN and WAN users.
+ z) v$ s2 Z% Z6 X% m• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
1 B& W% e) S. M3 K2 |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
4 |' c. E/ S+ f. w% N$ w  P• Ensure correct client maps
7 X( e1 W0 x" To Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
# M, [$ G/ U8 V  B7 E; m( wo Place client maps in the closest FSC group to their location.
/ o  C: q( i$ T; y* U• Use multiple FSCs for load balancing
; a, E. F# u. i4 @- |" n: v9 L- u# Co 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.
+ {; E! ~* c0 J3 l2 x0 B• Place FSC cache servers close to users
/ g3 i+ j$ B- g9 eo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
4 W: s+ ]9 e' |, c/ jo Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
  S# ~, F4 ^$ Co Greatly improve write performance (save time) over a WAN especially for CAD data.
5 X2 E* I! K& p$ M0 f8 _) |  |* t• Prepopulate FSC caches
& x7 b* L" U6 q# d/ V' fo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
: N2 X, ?9 ~: ~1 _, Q• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
0 F. p0 R* d" Po TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
- i7 A" L5 i% o8 ~# }! zo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
- p; D% S* K0 M/ C) J1 Z0 W! w• Enable FCC File Warming
5 m# a2 G1 C( @9 J. co Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
/ _' k' \  Y# \1 uo 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
* s2 c: n4 c4 D$ z- @/ r$ ?) r: U& uo OOTB settings are insufficient
o Applies to both servers and clients
# ?; a: L0 `5 m+ G4 z: ~4 s7 no Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
' `8 L2 N- _+ d  JRecommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
! s" t/ F" ?. R3 S$ i* PSee Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
" s  p; E; l$ j• Used to monitor OS, Teamcenter, and SQL use of resources
# N- F$ q: K4 @/ U" J6 {• 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
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
9 P) p% ?. i2 i" w: Wo Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
1 J# H# R4 f, e# Z. ^o Optimizing Teamcenter Client Performance
. |9 V" k9 R/ `2 xo Teamcenter System Performance Analysis
• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
7 ?( ~! n8 L! B! F  g: m3 X0 uo Best Practices for Running Siemens Teamcenter on SQL Server
7 E. g* ]( R) Z1 F% o http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
4 C; m) {' ?" {, Ho Siemens Blog on Technet
 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
6 c  f* r) [" b' \( h7 ?• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
7 c, ]7 u; |( N& oo Optimizing Teamcenter Client Performance
5 ?. K! M( V  c$ K, u0 ~o Teamcenter Database Server Configuration & Tuning
Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
$ [" B+ C  Y- nTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
, s1 N9 i$ w) z: }- \; e+ lAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
- O, P- X* s4 G* X1 }3 Y
/ a  L) n$ D+ o- `1 Y9 L

xiefeixiang

调优厉害啊

a150159

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