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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
5 ^4 p: _! K; c9 B) {3 Z' w/ Dhttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
( z7 T3 L2 r, V5 H
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

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
( R$ M9 S+ h2 Z5 g$ VFor those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
• Productivity – doing more work with less
o Improve end user productivity
, ?( o6 Y' R/ a" m- p. l/ l* co Improves administrator productivity
5 y* G/ V; @1 O9 n/ `4 C fewer help desk calls responding to or fixing preventable problems
• Reliability
( B# p5 W. u# F% Y+ Q  O  @o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
% |! r) ^) s% J. |1 Do Fewer operational errors/problems
7 N; |1 q$ B3 `9 \/ t8 u1 h• Cost Savings
o Less waiting means less time wasted.
  f. V% ^' M7 o, k- o) zQuick Case Study: Company ‘S’
+ v: K: R8 v: F# v4 }' K* ~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.
& G2 H* E' a" D- w0 N; Z; KSee my March 2012 article on PLM World’s website for details:
5 Q" F* w+ P+ n( T1 l% qTeamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
' [9 d9 b# L) i: _7 }2 K; ?Common Performance Bottleneck Causes
. L0 F* n: D& s. W7 x8 t' g& _Using OOTB settings — OOTB settings are intended for development environments; not production environments.
4 H; L7 D) ?/ d0 x% w5 T) POverloaded 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.
  {; s. ~/ x0 e4 GDatabases – The Most Likely Culprit
7 ^# s* Y) l+ \7 U  ]& v  Y• Database performance is highly sensitive to hardware, software, and DB configuration.
7 u( D2 d+ h9 ^5 m) d. L• 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.
6 W  q7 G' s' w4 _Mitigating Database Server Bottlenecks
/ N2 v' A0 j* T3 M• Must use dedicated DB server
" F% n& d0 c, `  p) ^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.
! B6 w1 D5 q- B$ \• Must have fast dedicated storage for DB files
: n7 T: A% f5 ?0 x1 }3 h8 @o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
4 ^4 t: @2 t! |2 l3 Z* P2 Q# Vo 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.
# E- L% ^" v( Y" C" qo Use disk controllers with a battery/flash backed cache.
" y7 ~; E; O2 x: L) Yo Use multiple disk controllers if possible.
• 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
- y, a5 U7 A0 W* l! Z9 L( Ko 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 T0 ]$ E7 c0 @- n$ w2 }& a$ o8 X& B• 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
o Update statistics and rebuild indexes regularly.
! R5 y+ f/ |; o# ]Common Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
/ _* L& O! x1 t2 T/ i6 @5 k, `; Y" t• Poor Web Tier Configuration
7 Z% u) U/ M0 [' f8 H- u% K# s% m• Poor FMS Configuration
• Debugging Turned ON
) v& _  |' B8 J: C- i6 [" o) E• Rich Client using OOTB settings
$ q" C) m$ P0 g7 u‘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:
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.).
- X) J" h( k! E8 Uo Set up multiple FSC cache servers to take load off busy volume servers/storage.
6 O" b/ x4 [/ h5 y6 \Web Tier Configuration
! N6 L6 Z' e( ^) J+ ~/ r: B& p• Do not use port 80 or 8080
/ _- e* @: u' g) Do 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
o Must be done on both web server and on clients to take effect.
2 D" G" Z  @' P. l8 u• Change/tune OOTB settings for Web Server/App
5 |9 q) \1 y1 [+ ~9 uo E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
  y6 r/ {( H; h  Y; k' P• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
• 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.
• Using OOTB settings
o For development purposes only, remember?
• Missing client IP address subnets
5 b; t0 x( V$ U, r9 d" `• No load balancing
6 L6 H) N& @+ @5 n* K• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
/ k7 g3 N2 }& F, y0 f1 a+ rFMS 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
( |! N6 a6 X3 `6 \& t3 r' q: m) jo Simply picking a total read/write cache size is not enough.
3 t7 y( J/ m: J0 xo 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
) u" n, b" u9 Go 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.
' F7 a: _, {5 I% u7 y• 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)
4 W  O& c+ S( [. c4 m' no Use redundant FSC cache servers to load balance each other. Also provides fail-over.
" I2 ]* \5 ^: z1 ~9 G9 Q• Place FSC cache servers close to users
; f5 k7 q+ b$ S3 C, B! ^9 {o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• 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
o Run a nightly script to prepopulate shared data across FSC caches.
- P( w) L& |9 H$ @; Q; BMisc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
* b1 Y: ^9 n0 P* S3 k7 `4 }1 Fo TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
• 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).
• Enable FCC File Warming
" a+ p1 T! g) _, y6 ho Improve startup time by having FCC and Tc files pre-loaded at OS login.
% j9 u$ y0 R6 H" S. G" D3 Z' pNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
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
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)
2 K2 \6 S+ T& X  H. F: QSee Presentation.
/ E: M7 \6 L7 P8 n% \( t4 Y: ARecommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
) v5 l2 K$ t+ a+ o) k! g• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
9 P% t* L! e* q0 }, O" u  ?$ F• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
( G. H: J; y, h2 c* e' c8 L/ |1 z• Sysinternals Suite (free from Microsoft web site)
) e" I* d5 Q7 d: {$ |3 c• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
% f* Z1 Q% P2 E• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
4 J6 U  V( U2 E1 So JBoss 4.2.2 Installation & Tuning Guide
) A3 f3 ~+ o; ~7 t) Z$ h3 _o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
/ X* Y3 t. ^: m1 e( G9 }• Oracle documentation & web sites
• 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
% E1 d; U: X5 w6 Go Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
5 n' A$ b& X$ x' i3 r http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
# U7 a: x1 z# K- L/ w• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
" }& J5 r+ Z& E: ?o Teamcenter Database Server Configuration & Tuning
Contact Information
  m" E2 p1 `, Q$ ILarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
  {3 B9 R* H  J' FTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
( D3 U: C5 \; t+ I( ]) a+ qAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
  g7 V; O$ J6 z+ H& X+ Z" G
& P) F; E: _; a8 k9 [

xiefeixiang

调优厉害啊

a150159

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