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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
* ^1 [- i$ m' ]9 D$ ^- v! m7 `+ Ohttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
  {0 J4 U/ U7 Uhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

' G) e! I  F/ B3 w) c: vTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
( r1 O5 O6 L9 P0 r* @
Larry 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:
& c9 j* v& h# VWhy Performance Matters
• Productivity – doing more work with less
8 o8 Y' x- {& P, a; Zo Improve end user productivity
: e: o% {1 T9 m2 oo Improves administrator productivity
6 N9 c% O. {( k' R) V fewer help desk calls responding to or fixing preventable problems
• Reliability
& k8 G0 u  D, N; Po A well tuned Teamcenter environment also improves system stability and uptime.
- O  |0 x! M5 j/ ~# Z/ O. Oo Less opportunity for data corruption
o Fewer operational errors/problems
% k( [8 {+ }( \• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
3 [3 w# B+ B1 u: aPerformance 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.
& g6 d* D1 ~' }* WSee 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
6 Y, p9 v! T3 \7 u3 BUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
Overloaded 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.
5 H0 y9 n( A9 C( FDatabases – The Most Likely Culprit
! J& C* @4 }  N• 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.
( g" m: U! ?0 m2 u/ IMitigating Database Server Bottlenecks
• Must use dedicated DB server
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.
$ T! I! l* M* J' ?• 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.
$ }. v: ?* p  z3 Go 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.
3 X9 W7 r) d4 h+ U) H' Uo Use multiple disk controllers if possible.
9 l; }# V/ S9 R; m. d0 h7 e$ `" E• Cram the RAM
o Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
, T% O2 ?: L( P. U& g+ S% Ro 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.
( n1 |; r- C: P• 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.
4 m" F9 ^* \+ T# t3 \$ f* A  h• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
; D  [9 d* E( LCommon Teamcenter Server Bottleneck Causes
8 A1 ^& {7 \2 Q, g) l( e• Overloaded Tc Servers
, E2 C7 |8 o6 F• Poor Web Tier Configuration
• Poor FMS Configuration
  E0 Q- A" I5 I  x$ F2 r$ i• Debugging Turned ON
• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
, y1 N5 l) z" ~/ w• Put Dispatcher modules on separate computers away from other Tc Servers.
. A3 q$ K/ \. [/ P# U/ w9 m% k• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
+ |: w9 ?/ s. i* ?6 n" l7 xo 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.).
" k6 w$ ~) |. |& ro Set up multiple FSC cache servers to take load off busy volume servers/storage.
+ F& K; B3 ~# l3 k$ ~0 N" dWeb Tier Configuration
2 [% y4 v5 A  p4 e9 g• 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.
6 a& C0 [/ T1 S  a• Enable http compression if not using WAN acceleration
0 S! A% i, n( K, ?0 W1 W- ro Must be done on both web server and on clients to take effect.
( j- v  S, Q6 K9 ~2 ^! l2 \1 v• Change/tune OOTB settings for Web Server/App
o E.g. timeout values, max # of threads, Java memory, etc.
3 p* v  n$ c# D, m- bo Read tuning guides specific to your chosen web server/app
0 h! F4 t4 w' j) k• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
0 i' @9 Y8 ^9 v% S- `: Y, dCommon FMS Bottleneck Causes
• Data improperly routed
+ I4 x2 s: R4 K6 a; Y% F; |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
o For development purposes only, remember?
" Z0 z2 r' x9 x+ j/ h% k• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
  \: O2 ?! ^5 q% ?+ {+ e) x• Not using remote volume servers for WAN users
. @+ \7 X! N) `, {$ p% w+ z% F, VFMS Configuration
" e/ j' v" m5 h' C( u( {• Ensure routing is correct
8 r/ @4 ~/ }/ x% {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
6 q5 Z, M9 `8 A' \8 c. x4 c+ c8 lo 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.
8 B" K0 ]4 H& p% ~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)
) L* P) Y6 d, [) ?" xo Use redundant FSC cache servers to load balance each other. Also provides fail-over.
• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
/ U* X1 T4 U8 z% `3 V6 P+ f• 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.
• Prepopulate FSC caches
/ O9 t1 R& i" [; O" O. R) e4 Y- [o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
  d- c. ?8 J. Z6 F' _• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
+ Y: i8 M9 }* a. po TC_SECURITY_LOGGING=OFF
$ e1 B1 ?7 R, ^5 @o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
, i; e5 K0 I; y4 l) y1 jo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
  q7 \) [+ r7 x! S) D• Enable FCC File Warming
6 e' s7 S# n. I2 ?; F% Go 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.
! u+ p4 W& t. d6 |) }% i% ^o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
% v7 C3 v3 W* L* v- h4 \• Optimize OS network settings
o OOTB settings are insufficient
% _; }0 X5 X9 Oo Applies to both servers and clients
+ k, [, B- u/ ro 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.
0 B! c% \6 f  u' j. o% U8 aRecommended Client Changes (Windows)
See Presentation.
2 n) r) w- j9 @. `* w3 _% gPerformance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
& t# ]8 ^3 f+ g8 f9 q• Used to monitor OS, Teamcenter, and SQL use of resources
' h4 J' U8 b$ J+ G& n• Wireshark (freeware network packet sniffer)
4 t/ J8 L7 p- B• 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
5 p  K% X) \) X2 m" m1 {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
o Optimizing Teamcenter Client Performance
  s  d9 C8 ]9 g$ Y( ao Teamcenter System Performance Analysis
8 s9 s) o# c9 N9 x5 W• Oracle documentation & web sites
8 K3 H/ w/ d& n1 o: B  Z  V• 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
% M2 A0 X6 q. t& vo Siemens Blog on Technet
4 q' |7 k. x5 A5 q4 z6 X http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
( _8 m1 X5 U& d3 q/ M- `- T+ B/ uo Siemens-Teamcenter-SQL-Resource-Page
4 T& @( [5 H, V9 c/ V  q 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/ z+ O$ a4 z( w) \2 j" to Teamcenter 4-Tier Deployment – Best Practices
) R- }0 G4 L( F; l% Wo Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
( U) t0 d- ^  {# b& Y+ f+ M+ Vo Teamcenter Database Server Configuration & Tuning
. C) F  R; i. T7 R$ A9 }Contact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
4 _$ ?+ x7 X) N6 _8 Q8 C- jTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
& D3 F) H7 n2 J2 Y* j  RAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
5 z' o; t" w  U" l2 H7 K$ |& s  r) _# s
# x' `  W2 E, u1 j/ p5 k

xiefeixiang

调优厉害啊

a150159

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