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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
: Z4 M* }7 N" d- h) \$ D6 [; ^http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
( F* z5 E/ j! j! q8 X
4 [9 F' I) T6 u" c* lTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

5 C/ `1 k  t/ t+ bLarry 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:
2 ?/ c; v1 t9 D5 _+ e. iWhy Performance Matters
! I2 _, [  d" S+ Y! S! \• Productivity – doing more work with less
: |: c4 r) L5 zo Improve end user productivity
o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
2 [! Q& h$ J  _5 N  n, k) @) d• Reliability
0 V# k: r6 A. O8 \5 [0 s: a8 po A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
2 v! C! I% X* U$ P) ^0 p0 co Fewer operational errors/problems
• Cost Savings
( a: y3 [6 p0 b! yo Less waiting means less time wasted.
- }0 `* v1 \: }) j  OQuick 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.
6 J- c( C& O6 F, }5 \9 nSee 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.
1 _- D# K; m0 U0 g: B5 s7 M; `Overloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
9 ^" y( T8 \/ Y! B2 RLack 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.
- p7 r. X9 N" j& J& |• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
4 C2 {( p9 @* y) a6 ~# L- H7 PMitigating Database Server Bottlenecks
• Must use dedicated DB server
: {7 q- H2 |+ E- K3 Q' a3 Ho Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
+ K# }3 k1 S2 ^0 i/ W• Must have fast dedicated storage for DB files
o 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.
o 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.
1 I1 M( I" T% v; f" q  Ko Use multiple disk controllers if possible.
% X6 z( A% H9 H3 O• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
& e. u/ H" k) Q• Use 64-bit OS & DB software
# q2 f: e. A2 e2 [' a. ]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.
1 h$ }( h8 n0 S  o9 N3 w• 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.
* f' F( U' _) m! ^) {+ s/ l• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
  D( d+ ]" q5 o+ ZCommon Teamcenter Server Bottleneck Causes
; ~  _' v3 Y% P, }. X  `• Overloaded Tc Servers
0 F  F4 \7 X" |- N; D• Poor Web Tier Configuration
• 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.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
$ [; t* {0 S8 y6 ]• 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.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
0 B9 {, [4 T& w7 XWeb 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.
# b; Q- T# {% ~& @- t• 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.
o Read tuning guides specific to your chosen web server/app
# c/ z- K9 {" @) m" G$ a• Scale it up or sideways
2 d% e: w7 O  M- t3 o6 c% Go Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
- ~. j& e7 y& v9 {Common FMS Bottleneck Causes
. ]6 n, l: V1 p• Data improperly routed
9 a4 j9 c# |" Fo 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.
$ }: G0 Z+ c# v% T& N1 m• Using OOTB settings
! h% B5 r; i) c" S( r/ I0 }o For development purposes only, remember?
- j8 g1 _5 r7 v% X• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
1 g$ `) D5 B3 h+ y9 T6 g' R6 F) BFMS 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.
o Use correct transport algorithms for LAN and WAN users.
• 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
• Ensure correct client maps
6 e' b5 [" K* M; o: d* M/ |o Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
. G+ z$ p$ z$ b( z% }o Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
+ I1 f9 b+ @9 F: ao 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.
7 Z' t0 F0 J9 s0 _/ h5 m• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
, {/ D. z" J. b" F% {o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
  X6 U  M7 b/ z. B) ^o Greatly improve write performance (save time) over a WAN especially for CAD data.
• Prepopulate FSC caches
% ~/ B7 J  i' I) Wo Run a nightly script to prepopulate shared data across FSC caches.
3 B! O3 o7 ~2 \$ {( H1 P" \5 |! IMisc Teamcenter Changes
8 B8 J% o2 z7 U& E! Y• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
; k( u; ^: {/ e2 n1 _$ }5 ]o TC_SLOW_SQL=-1
8 h4 m% H# O' w! W1 `4 V* g! ]• Rich Client ‘Teamcenter.ini’ configuration:
9 s- Q! A: i6 d% 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).
8 [) @2 F5 T7 y( X• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
. A' Y( y% a7 w5 {( NNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
- w9 L/ r2 M4 s+ L: Z2 k, L' {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
$ E7 l  J! }6 F/ co OOTB settings are insufficient
9 F8 `3 n7 i8 Oo Applies to both servers and clients
# Z6 }# Q6 P  X. X5 l9 ro Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
- L4 E6 m- a  k5 M& uRecommended Server Changes (Windows)
5 C5 f: V5 O  W' S1 s6 s$ ?See Presentation.
Recommended Client Changes (Windows)
8 x8 D) _3 C' K0 y4 r7 NSee Presentation.
1 _8 k6 Q7 c  ~& h% L+ oPerformance Monitoring Tools
2 y: F- Y% d* e6 E• Some useful performance monitoring tools:
5 }# i$ V+ k& G; j! f• Performance Monitor (comes with Windows)
8 G8 P6 |- b$ _2 {* w& ]• Used to monitor OS, Teamcenter, and SQL use of resources
1 _" t4 y- ~4 D4 @8 d2 U, P9 a+ ^! w4 _• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
' O5 n$ D4 c) |3 `8 H! a0 x• Available at http://www.wireshark.org/
7 z$ k6 B" V# ?/ e0 m• Sysinternals Suite (free from Microsoft web site)
: L/ Z0 ]! c5 b& x* L, `. u• http://technet.microsoft.com/en-us/sysinternals/bb842062
- |& E8 h& @+ ^1 d( ~- @Reference Materials
6 t& [; g& {+ m  i. V6 j• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
. _4 V" P' J2 O+ G( }3 U/ jo Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
  k+ @- @, a: Y- z+ w  w. Fo Teamcenter System Performance Analysis
• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
9 w8 B4 D) y6 C4 p( |o Best Practices for Running Siemens Teamcenter on SQL Server
( a1 X. ?$ T3 i0 p- B 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
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
1 C# I: }2 H0 S  Y0 ]! Bo Siemens-Teamcenter-SQL-Resource-Page
3 T( ]6 I- o2 I0 `/ j* \ 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,
' v/ r4 O& N/ w9 Y5 Bo Teamcenter 4-Tier Deployment – Best Practices
' U, S, ~8 ]0 C& P9 eo Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
3 x1 @0 N7 a0 m0 J- xLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
+ n. O. ?' {  [4 y; s$ a3 rTeamcenter 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
9 X1 L9 m5 G7 }+ w9 C
, r5 w, G! H! c) V  C# l! z( h

xiefeixiang

调优厉害啊

a150159

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