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
0 e' ?7 ?; E- [0 mhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
/ @" h$ G. ]# A" @8 |
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

: ]+ N) W& b6 N4 w, ~# 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:
) B4 l/ v& s5 d1 E0 ]$ O, l) p3 [Why Performance Matters
• Productivity – doing more work with less
0 Y, }8 N' l& t: M% Fo Improve end user productivity
# N8 S% k4 N+ Y$ P3 o8 Po Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
( D) f' c5 W" W5 S, l/ t( Zo A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
6 j! y' o) w9 ^) n& A: So Less waiting means less time wasted.
1 x" g' [5 C! CQuick Case Study: Company ‘S’
3 v) q) D0 I. T5 t% j8 g. f0 XPerformance 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
, v8 c7 F* w$ G( CCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
* `# r; P- C1 j) @; b0 {5 F: [Overloaded servers — Putting too much on a single server.
Operating system settings — Network settings most common (e.g. TCP parameters).
4 y, I1 G0 P$ z; i% YLack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
" Q/ u5 {1 E2 k) B+ S2 d' d9 `Databases – The Most Likely Culprit
8 c# A. \; Y! ~" i0 I• 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.
" m3 ]+ I) h+ Y4 x& v5 p3 w- ~• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
' @+ Y: M2 w0 f: l0 m7 rMitigating Database Server Bottlenecks
• Must use dedicated DB server
/ I* b" S; q' i2 b: F4 ~% m6 uo 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
7 x% T& K: N& `( I% C$ \- uo 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.
" H6 N- o& y* }. \1 w  W2 _- ]o Use multiple disk controllers if possible.
• Cram the RAM
+ F8 L2 `) _) H, L$ K7 U: @o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
  q/ {2 Z6 K* i. j" ~" I) |# l• 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)
, m9 U# c% t3 p) Po Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
4 U9 B* L% U; V& a& ]9 y0 q• DB maintenance tasks
3 }( x4 V- b% ao Update statistics and rebuild indexes regularly.
* v2 x- ~7 M4 r" iCommon Teamcenter Server Bottleneck Causes
- Q, b4 V; _5 S) R! F8 K• Overloaded Tc Servers
• Poor Web Tier Configuration
$ O+ _0 d( p4 a$ S$ m( E• Poor FMS Configuration
• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
7 O6 N, d$ r' l* S" Z- f3 @• Put Dispatcher modules on separate computers away from other Tc Servers.
- V' \' s* V. h: n• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
6 ~# i1 K. x( f+ b) C8 v: X2 c  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.).
+ q& Y; I1 r$ i1 ro Set up multiple FSC cache servers to take load off busy volume servers/storage.
1 p0 X. F- m6 x! a% D  K7 ]Web Tier Configuration
* Q8 W! ~: Y( L6 }# G• Do not use port 80 or 8080
' b+ I  f/ W  J9 ~! Lo 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
* G9 f& {5 X9 [. {6 r9 }  z6 |' go Must be done on both web server and on clients to take effect.
5 y, v6 P$ {! L$ ?! S" u• Change/tune OOTB settings for Web Server/App
+ ^: R/ c; R  Ro E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
' k4 I3 h2 ^" }' A" Z! I' Y• Scale it up or sideways
4 z1 m+ i+ ]+ Bo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
, s) V8 s9 C% Y- y5 ?1 b• 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.
  q1 w& |7 q+ `' P1 i: @. M• Using OOTB settings
o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
1 W' S+ d; Y8 }• Not using remote cache servers for WAN users
9 m+ J  O$ R: A: K3 p: v4 S# p• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
( N6 F: q' |+ e& }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
. m9 F& G9 ]" u! x9 a8 So 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
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.
• 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)
. @7 t+ D( X1 ?5 V% G8 ro Use redundant FSC cache servers to load balance each other. Also provides fail-over.
- L7 w% o+ C6 b) Q• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
$ a( d  }6 ?$ u1 z; b( `+ R• Place Volume servers close to users
8 @, z0 Q7 V3 J8 fo Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
& N7 p* j, ?9 n" j: r; f5 wo Greatly improve write performance (save time) over a WAN especially for CAD data.
0 G! N8 \" T" \  k: P• Prepopulate FSC caches
o 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,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
5 x0 ~  ?' w0 l8 |& z. b. o! Y  y% lo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
( q2 w1 u5 n# \( \6 h• Enable FCC File Warming
8 h# _* Q- [+ ^' _# d* U. ~2 }o Improve startup time by having FCC and Tc files pre-loaded at OS login.
; O6 \( r2 H2 Z2 s* f  UNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
  M; W2 |/ E) e  q; j* wo 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
o OOTB settings are insufficient
/ ?5 V2 Z' o( I" r& Y1 E7 lo Applies to both servers and clients
( Y- p: y% w5 c! L% Qo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
$ y8 V* O# p6 b* {+ I$ ~4 rRecommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
; R1 |! j: k2 n/ W: a5 E; rSee Presentation.
- i9 f8 I& M* T8 u- Z$ k& w. qPerformance Monitoring Tools
• Some useful performance monitoring tools:
) [7 X) ^% s( x3 O1 g• Performance Monitor (comes with Windows)
2 n+ L+ i' C8 }1 _• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
9 Y4 _. c( ]3 p/ c+ T• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
& h0 |& T8 e/ |5 G; J( G" O• 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
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
+ o3 i  ~& O6 Q1 Xo Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
• Oracle documentation & web sites
7 q+ A- Y( e0 q( P5 ~8 b+ V, E• MS SQL Server documentation in addition to:
o 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
: D$ K5 O0 F  P9 c. to Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
- _1 l- \: c3 Q- c7 f% X8 L 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
# T/ {/ x& d+ W% l* o' V: W: Wo Teamcenter – Database Performance
1 y! ]; J5 l$ \8 ^. Ao JBoss Optimization for Teamcenter
# i& q! w7 y) [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
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

1 _7 J; S" K) h3 w+ V; S- K

xiefeixiang

调优厉害啊

a150159

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