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
& D. P  h' R0 M& @! M( Mhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
( j: I6 T) N* u* s4 {
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

6 U( k4 T0 P, j# O  y4 Z/ Y& cLarry 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:
Why Performance Matters
' ^; P6 z  a1 o0 F• Productivity – doing more work with less
o Improve end user productivity
o Improves administrator productivity
8 S1 T* H: I& d# {1 U fewer help desk calls responding to or fixing preventable problems
) A" {" K3 a7 W9 x) e' |  C  T• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
6 N+ p& C9 O7 B) ]( Bo Fewer operational errors/problems
7 q) g; T( R4 Y( p# R• Cost Savings
o Less waiting means less time wasted.
' C4 ]+ ~& `5 b2 K8 X5 QQuick 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 W$ x" U' X6 D* y1 ~1 D! |" fSee 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
: z4 k6 J7 y* j+ s; k5 QCommon Performance Bottleneck Causes
Using 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).
3 U: C* R" Q% d4 cLack 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
; X3 a  ^; I6 S- `' u1 R( I$ j+ t• 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.
7 k! ]! m. M" r- d, aMitigating 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.
• Must have fast dedicated storage for DB files
. [% P7 B6 P0 @6 U8 q) d$ z) Jo Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
/ E) M6 P, b5 A) 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.
6 P* [6 _% F/ |% M2 m- j) d3 M- ]! @o Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
6 p1 j+ t" u9 T3 s0 G1 M• 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
8 X$ k6 G. g% U4 z+ P# }' ?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.
( k5 N& i: d  U+ K# Y0 @1 Q; o: [( ]• Use a good quality network adapter(s)
0 h% m& f' c/ |+ ?: io Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
& @+ z7 r! x' K1 \  Z9 U  Y• DB maintenance tasks
- @' P! S9 k, q, d6 y# So Update statistics and rebuild indexes regularly.
; `4 t" @  H& [: ?4 N- ICommon Teamcenter Server Bottleneck Causes
2 \$ Q5 G5 t4 e9 X6 C1 i• Overloaded Tc Servers
  d. W6 u: H$ c& N! C% {% U• Poor Web Tier Configuration
• Poor FMS Configuration
' K7 X+ W8 `$ L; G0 z• Debugging Turned ON
• Rich Client using OOTB settings
' k! ?; X" s$ X. B! A‘Unload’ Overloaded Teamcenter Servers
- }3 p" w/ d7 J% t1 L• Put Dispatcher modules on separate computers away from other Tc Servers.
5 H1 I8 D' l5 }- ]• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
• Use load balancing for Middle Tier & FMS:
$ F0 j, g) s- G5 ^" 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.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
" |$ U9 L/ W% [4 `' q  x• 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.
- e7 D. \! Q; r9 _) Y• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
7 w! U- v$ V, D; a: U' u• Change/tune OOTB settings for Web Server/App
o E.g. timeout values, max # of threads, Java memory, etc.
) x# t4 c; ?" _9 n9 s" vo Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
5 W. f& M" X  o: c5 K, |. k$ Do Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
% ~, _5 |) g( A6 B1 t0 s. j7 a6 _  eCommon FMS Bottleneck Causes
/ j8 G1 N& E5 _# c) s• Data improperly routed
3 a0 d6 M# G' U5 po 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.
6 A7 x4 \2 W0 i. l( r1 |• Using OOTB settings
o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
- l: E! b& i# {1 }• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
4 w" x9 L* Z; ~; E! m7 D5 ]0 O• 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.
; D' _0 [/ N* o2 xo 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
- H1 Q% X( H8 \: M/ c9 G! }% f• 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.
, Y7 h  Q% @$ Y7 c# P2 @" n; w0 i• Use multiple FSCs for load balancing
" p  ^  T. x5 P$ `; I( c, No Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
* e0 ~( |* M6 J$ z7 Ao 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.
• Place Volume servers close to users
$ J8 J1 E1 A1 n. A2 l, fo Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
/ i7 A. v3 m8 N! ^. Ko Greatly improve write performance (save time) over a WAN especially for CAD data.
7 }% m- \+ a) L4 W/ z; H: x# v• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
% h4 [$ ^  [- f• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
4 [! q0 G# n' qo TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
7 `' q- o( |% U' Y1 ~2 f; Bo Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
/ j: _; i3 G7 Z7 g" j5 B" @• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
2 a% \2 v  {, i* o8 |: j* Q- d) kNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
0 `  f3 a: e0 q( [8 R$ U9 co If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
: x- x5 r5 s1 ]# F+ H$ h7 `' a• Optimize OS network settings
o OOTB settings are insufficient
, w# C" p8 p3 X; No Applies to both servers and clients
0 }+ G/ z8 U, K8 \$ R  o3 e* [8 Io Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
2 w0 A/ P. m8 R/ t3 ?; DRecommended Server Changes (Windows)
6 N. m$ u' ~/ z4 I' }% ?) OSee Presentation.
1 K1 c4 j+ s1 q& F$ j& rRecommended Client Changes (Windows)
, n  [9 t( V( f6 f& WSee Presentation.
8 E1 y0 C/ B7 A7 p; N% aPerformance Monitoring Tools
• Some useful performance monitoring tools:
0 z9 I7 j/ U0 ?, D• Performance Monitor (comes with Windows)
; O( N9 H# Q  Z, Y# g' r8 I) }• Used to monitor OS, Teamcenter, and SQL use of resources
  |1 C$ w% c5 N• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
: @: Z3 P3 j+ Y9 g• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
5 [" T, {3 R: n4 h: I8 S' |- _( \• http://technet.microsoft.com/en-us/sysinternals/bb842062
$ b* b+ C  \5 P. y# K. A8 \1 F2 E& ^Reference Materials
& ^4 p! I5 ~4 ]• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
+ K, C4 D% E/ |! H  C- ^o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
! J: g' ]5 ?% j; f) do Optimizing Teamcenter Client Performance
- E6 O, d/ ^& Z3 Xo Teamcenter System Performance Analysis
  I3 H0 p" o. [. q5 H0 Q• Oracle documentation & web sites
/ A* ?& g3 t3 p1 R$ n4 Q+ X  C• MS SQL Server documentation in addition to:
. U' r, T" }; U# ?% f1 _2 o0 E, 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
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
$ m. v; F7 N6 X4 vo 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
- c+ U; V3 W7 y" \o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
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
+ w, r& I. I: y5 x( b. wTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
! L. Q" y4 T- m/ M* y7 e2 F3 cLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
  L- M" g! b3 @" ]3 h* vAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

xiefeixiang

调优厉害啊

a150159

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