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
2 |" g; C: p4 B, L* P3 m- _% Ihttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

! T4 G* R, `4 C- STeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
. [% d3 e! O3 e! R8 T1 V
1 o! G9 k) p# f( |* N7 kLarry Carpenter
1 [5 Z7 Z% {5 ^) }0 FAt 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
! L9 y7 \) W. H1 XFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
( h0 x' p1 t! T3 @* b1 HWhy Performance Matters
3 h, F' S2 d: s8 J  g• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
6 |2 q. N: F% d" w fewer help desk calls responding to or fixing preventable problems
0 ~+ U9 k, K2 d+ P6 p• Reliability
4 V8 ]6 c# ~1 _$ I6 S, ro A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
) Y. n7 [$ K2 Yo Less waiting means less time wasted.
Quick Case Study: Company ‘S’
2 ?6 r8 x8 c& i! y  j5 H. ^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.
' b6 `5 @; I7 NSee my March 2012 article on PLM World’s website for details:
$ j. y$ z' w1 \Teamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
Common Performance Bottleneck Causes
) n! C: Z' N6 L, X5 L" V- G* PUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
4 |% G) N! R  KOverloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
. w9 i" f5 L: j+ \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.
9 N2 R4 J* L2 i$ x% s) P: aMitigating Database Server Bottlenecks
• Must use dedicated DB server
- v. R* P( R2 K; ^. 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.
; I% k- C) [: x5 j/ P" G7 {: p• Must have fast dedicated storage for DB files
( e/ y; B) O6 bo Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
, t# \2 W8 W7 G6 U$ u- }o Use multiple fast disk spindles partitioned with proper RAID levels according to the DB vendor & SPLM recommendations.
. l9 C' D: l! }# l9 F  J+ no Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
o Use disk controllers with a battery/flash backed cache.
* Y4 ^* d/ _" e; e) B0 C, Zo Use multiple disk controllers if possible.
6 e. u6 I6 w( X: m' q• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
" X: g, l" X+ E- f• 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.
! G1 O8 \2 R: X• Use a good quality network adapter(s)
: r2 @1 ]! j& F6 `( N, M6 |o Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
& o; g/ X# p8 o5 @5 z8 [• DB maintenance tasks
3 K" {' M* t4 b/ h; T- s* ao Update statistics and rebuild indexes regularly.
+ o7 y& C0 ]6 X9 wCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
3 T/ e) {* k0 a$ w• Poor Web Tier Configuration
+ ~# Q1 {* u$ A% m4 |  l• Poor FMS Configuration
• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
• Put Dispatcher modules on separate computers away from other Tc Servers.
, d& U/ Q- O7 F9 k; h7 ^• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
' f, }1 Y: a; p# ?) ^7 c5 W* \% r& B0 vo 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.
2 x! ^/ e6 V7 V$ a. g. kWeb Tier Configuration
( J! C) u& L! a: y7 K. f9 i• Do not use port 80 or 8080
) S" m; q: c& I& g: d6 V5 {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
3 p3 \* w3 g7 Do 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.
o Read tuning guides specific to your chosen web server/app
! T8 F& }$ a, A5 e7 Q, G) B• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
1 E% c0 F. y! O5 ]! U! o8 CCommon FMS Bottleneck Causes
4 e: n, K0 j1 d4 L! G) K( M• 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.
2 `2 ?: u0 o+ E1 P9 v2 [! z• Using OOTB settings
- e/ @* n. w& t) x: do For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
3 Z) c- X! k6 ^: m- j9 U/ U• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
/ C0 T7 K, N- P( ?, @- KFMS 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.
) R  e+ w8 C6 U4 i: }0 Q5 w8 \: Ao Use correct transport algorithms for LAN and WAN users.
. u, z5 D( b7 b$ \0 E• Tune FSC/FCC cache settings
* \4 z7 _/ l$ z/ F/ V8 s1 s( T, xo Simply picking a total read/write cache size is not enough.
& C  [* ^) c  j( G3 u3 \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
• 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.
/ }4 v8 F/ M/ ~0 ]- S. w9 z7 No Place client maps in the closest FSC group to their location.
* o; x2 F$ K/ }/ Q• Use multiple FSCs for load balancing
/ V+ e9 k* }! m3 r7 S  zo 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
$ t! h& y% s" u& T; fo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
: I" d- d: k& i4 ^2 y1 s• 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)
o Greatly improve write performance (save time) over a WAN especially for CAD data.
6 ~: z! j: l" x' F• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
. N5 P- W3 O8 K1 r9 ]( h5 u: h6 tMisc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
7 \6 \0 C, s# fo TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
2 E& j& O2 v4 ?. ?; D2 F9 Y1 }& Eo 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
7 D. g! `: a! \/ d8 w, lo Improve startup time by having FCC and Tc files pre-loaded at OS login.
% m3 d6 [* _1 P; v% _  x: u  M$ xNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
2 @9 u) D$ t, j: v# lo If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
6 W9 j& |2 Y' y" N- \) O( Z, O: a• Optimize OS network settings
+ z$ h9 [0 v0 N4 m4 j$ O/ Do OOTB settings are insufficient
* M4 x# p1 R& l* t+ Bo 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
0 k% s+ y5 ^) o: M6 vRecommended Server Changes (Windows)
See Presentation.
; `+ C6 r' ^( l3 M) A3 A1 X% TRecommended Client Changes (Windows)
( m% C/ Y8 i  c9 {$ ESee Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
& g8 j5 [) f: k; H( K' T  d5 M5 K• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
; {& }; Y: d3 L, T/ {• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
8 r2 r. E6 ?) `+ b9 t• Available at http://www.wireshark.org/
0 T8 U) m/ m4 B/ n' z& I4 v6 ^* m• 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
  D; H% y1 C: D5 H% X5 wo Teamcenter Network Performance Tuning
: ?' y/ y* O9 q5 to JBoss 4.2.2 Installation & Tuning Guide
& f1 S/ a8 O8 Y8 P7 }! h& Do Optimizing Teamcenter Client Performance
, q' o$ J. [! S, ^& To Teamcenter System Performance Analysis
& Z0 r4 R; S! M; L' ]• Oracle documentation & web sites
8 q  g# R7 l% f/ {( I• MS SQL Server documentation in addition to:
o Best Practices for Running Siemens Teamcenter on SQL Server
  \7 ^# I# a0 b http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
5 p: k  `2 J; }$ g1 n' }! X" Bo Siemens Blog on Technet
) f$ @; r0 d( \) }1 I http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
3 C2 t5 V4 N. L$ _8 E8 Do Siemens-Teamcenter-SQL-Resource-Page
6 L3 \% y) p  G8 L- Y http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
' B& I5 X2 e- l$ v. I% L• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
9 f$ P- x1 D" h5 C3 xo Teamcenter – Database Performance
/ Z- K% b3 z( M$ D( Q; jo JBoss Optimization for Teamcenter
) M! X4 ]' H6 H- d) w2 R# ?o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
- l: v9 }( P" ?: `, Y6 R) ?Contact Information
1 v8 }( Y6 U  I8 o9 F' @% ]$ dLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
8 C# ]5 Z5 v1 j" LLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
5 O/ n& j- L2 h

xiefeixiang

调优厉害啊

a150159

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