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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
; M" c* {* r7 S. U3 J; z  hhttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
7 C& Y( K* L8 D
Larry Carpenter
$ f: O  W! J- @3 t, jAt 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
7 j4 [: a! i/ f0 v• Productivity – doing more work with less
o Improve end user productivity
( B% b4 x) t" `- m$ h0 _- O0 x: no Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
- m' M) U2 S* s/ t: @0 ~o Less opportunity for data corruption
o Fewer operational errors/problems
# K4 e1 t, Q; v/ c% g. I* ~• Cost Savings
0 _6 ?' u7 L% z0 b( ^o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
8 x; y- H2 I5 s/ C! D; P- R! B; ?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.
! V- ~* e- p8 [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
Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
' V3 J3 L5 h4 A: g+ j6 r, vOverloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
9 l7 a! M  B' ?. o  |7 PDatabases – 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.
* V5 M2 V8 u4 y& RMitigating Database Server Bottlenecks
, x: [: m7 B" d6 Z2 b' [• Must use dedicated DB server
# {+ }3 M2 M, V  C8 bo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
  b) {% e: H: p& V% ^• Must have fast dedicated storage for DB files
3 A& H" u; b3 O. I: q, Io Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
  _4 n+ E/ X5 F8 S* n3 I* g' n7 L' Ho 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.
( W& @5 r- @* |  W# e3 yo Use disk controllers with a battery/flash backed cache.
9 a. ]  @( v  q1 c/ }% |3 g8 k' So Use multiple disk controllers if possible.
( r6 x& V: v8 ^$ ~6 c  \: j• Cram the RAM
/ ~2 ~: P5 I1 q. n6 C3 Eo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
' \' \9 ?* I9 n. 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.
• 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
' U8 T$ R. i5 ?o Update statistics and rebuild indexes regularly.
* y# P) B2 N2 g0 |# TCommon Teamcenter Server Bottleneck Causes
8 o3 s% N% @; x* K. i• Overloaded Tc Servers
0 _' U- i2 |' X2 K" Q2 j1 f• Poor Web Tier Configuration
• Poor FMS Configuration
• Debugging Turned ON
$ I/ K/ c0 V6 r• 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.
• Use load balancing for Middle Tier & FMS:
  l. v2 o( Q9 H2 v4 K+ p0 ro 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.).
8 s3 Q; d* k- h1 c  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.
+ K% o! w" t& Y) q9 t" @. u" ~$ H  N# \• 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
• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
/ }) C$ a' R5 a6 [/ g/ b6 gCommon FMS Bottleneck Causes
" f* ^0 L# R- ~) ?! N• Data improperly routed
% j1 O+ r6 }, z9 c9 do 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.
9 I1 C3 j1 f/ t4 H3 h3 G7 q5 H• Using OOTB settings
4 x8 P" Y3 a7 x' L7 W6 l! b$ Ko For development purposes only, remember?
  H& U, |# ?/ C; X• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
+ u$ z: G7 t3 ^/ V, |7 v2 h% i3 `• Not using remote volume servers for WAN users
FMS Configuration
0 `2 S6 {# l+ L) M4 ]1 N2 k( B• Ensure routing is correct
6 [; `; Y5 \- s, po 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$ h9 ^: h$ mo Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
3 B' [1 c" z- Z) t4 r( X* n; C0 fo 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
& n; ~# i" P, D, p) k/ o0 L• 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.
o Place client maps in the closest FSC group to their location.
! }' Z5 T1 a$ A5 z" u: p• Use multiple FSCs for load balancing
; |- J1 x- B- 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 p4 n  i% v$ N• Place FSC cache servers close to users
+ L) w5 K: S! vo Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• Place Volume servers close to users
  ~% \' n* W' k/ z3 X/ ~3 Wo 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.
& u" n4 c" i5 t6 g7 h+ c• Prepopulate FSC caches
/ S1 `( y% k6 Yo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
4 A4 d9 J8 x7 Bo TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
7 s+ _$ \: k- y* X' K) To TC_SLOW_SQL=-1
% y4 J$ n# _$ t6 ~2 ]! Q! o7 q* {8 D• 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).
; n. p; _0 D$ A! n% [- N- X• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
& G3 a& ?/ v" t' l* @$ b* S' v. f# hNetwork Performance
+ o6 R/ h- p( G8 y& X. P. g5 P• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
8 w6 P9 Q# h5 f8 S- [# Zo If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
4 j7 y/ N9 ^- k  V" b3 r• Optimize OS network settings
o OOTB settings are insufficient
o 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
Recommended Server Changes (Windows)
See Presentation.
* ]* `% Q" M, Z% b) zRecommended Client Changes (Windows)
0 [9 F: g* `+ ], A6 |See Presentation.
3 Q0 p3 ]9 W% E6 h9 r' d6 [Performance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
2 K/ B( W7 k$ R% J% E! H9 y, L• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
! _3 x2 b7 E/ l4 I  ?• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
9 {8 r0 s: t/ D$ G7 `• http://technet.microsoft.com/en-us/sysinternals/bb842062
  m1 K+ G' b; m7 u" AReference Materials
3 V) L7 G0 ]8 y• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
- G- F1 m& B2 ]; Yo Teamcenter Deployment Guide
7 Z0 J- c" G. U5 S* }o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
/ y5 _! v) h( n. s; Do Optimizing Teamcenter Client Performance
: ^; a- W) f, b2 I8 go Teamcenter System Performance Analysis
4 Y, `" Z, L3 q) _) l! s2 E9 K4 @8 |• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
0 A1 g( y  t4 m) v# p* V- lo 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
6 `( {8 N* ~% H* D0 B& r http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
6 ^& M2 t1 I6 v, d& |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
o Teamcenter – Database Performance
0 _+ M7 ?4 B2 \1 v9 go JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
4 t1 T8 L* s- a* ?* Z! Y/ CLarry 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
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

6 Z7 U7 e3 T7 z2 z/ j# x* q6 C1 X' T

xiefeixiang

调优厉害啊

a150159

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