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
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
3 ~" F( k! f- O: Q0 W
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
% |6 M( Z7 \( p
Larry Carpenter
1 ?, {; V# _% ~; W( Y+ z, ZAt 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
• Productivity – doing more work with less
o Improve end user productivity
+ L5 g0 v. s6 Vo Improves administrator productivity
0 e' ~% y4 j  Z/ U6 _1 F fewer help desk calls responding to or fixing preventable problems
• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
( i2 W8 f3 j2 U" `o Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
/ u8 ]% V1 {* H* Q. x. t3 JPerformance 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
5 U3 N8 }, S' e9 ~4 o, a0 ^Common Performance Bottleneck Causes
5 g) L! }7 T# F0 M! r5 B. KUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
6 a! x# x$ A1 R1 c' \" _5 xOverloaded 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.
$ [4 M3 g7 t: }& k' O+ iDatabases – The Most Likely Culprit
/ f9 R1 @8 T6 \+ w4 W) O- |7 X• 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.
' d. {- ?; n' K3 K• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
) a( J: k- C- V& }7 ?Mitigating Database Server Bottlenecks
• Must use dedicated DB server
1 ]( K+ F- u9 ~* \0 \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
( v) h/ b0 g) v& H# o& D/ Y6 Mo Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
* r3 r( \' m( e3 Zo 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.
$ i/ g7 L2 P: B' B, eo Use disk controllers with a battery/flash backed cache.
+ l3 W7 ~  }" O' uo Use multiple disk controllers if possible.
• Cram the RAM
( L6 d7 e% m2 Jo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
, ^* z1 U0 x/ K- ~: C• Use 64-bit OS & DB software
  I) b. R- T& ?0 Z/ T; w, Vo 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.
4 x* l3 C1 q8 B5 E/ {1 Q• Use a good quality network adapter(s)
' @5 v/ d) ?0 y9 o6 `8 _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.
8 E. ^" }0 u6 V$ A% h# {Common Teamcenter Server Bottleneck Causes
3 |# \' M* N" T5 Q! m- l. M• Overloaded Tc Servers
• Poor Web Tier Configuration
& I: |; ^2 B! X. q• Poor FMS Configuration
% p3 Y! h6 S. \; f& J( L; |- |• Debugging Turned ON
+ E) v! [. M1 ^1 U• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
7 W* B, \+ ^6 P% y+ e& S: E! s• Put Dispatcher modules on separate computers away from other Tc Servers.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
5 W' E' x3 W: a• 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.).
o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
5 f* x3 M$ I! P) f• 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.
' o* m9 X, h" E8 ?! G) C2 Z& Q3 q$ P• Enable http compression if not using WAN acceleration
2 z3 m3 }/ s. L3 b, B3 D& do Must be done on both web server and on clients to take effect.
5 D. O. ?: S& ~9 Y- j( j• Change/tune OOTB settings for Web Server/App
: _/ g; \+ W' k3 y( F2 q: Q, Y0 y' Ro E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
( X8 X  ]% D* N" R0 \( e6 U• Scale it up or sideways
2 p" [! d2 N, G  zo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
. T& L: S% n- S2 R- \) X+ S% O$ `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
$ x/ y5 X. m. p; ?! }o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
0 v+ C- ]* ]/ f: ], A, S• Not using remote volume servers for WAN users
9 R' S# V! v. a, W, U: BFMS Configuration
, O; C: V( h" v8 |1 J% g• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
( f0 \6 W+ b4 o2 y* X  Oo 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
o Simply picking a total read/write cache size is not enough.
7 p  L( G6 B% go 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.
4 U; }3 `# q5 _# [o Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
, m# T. s: _) e0 t: ]0 y% i% `  wo 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.
• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
$ I% I' ]  P4 P" i! i: z• Place Volume servers close to users
7 @2 y6 X' K8 X- r  G! Xo 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.
% N! P" @4 f2 V3 }5 U( i  L• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
3 P7 Z% K* X- e• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
5 [* x# l8 i, x. h( Vo TC_SECURITY_LOGGING=OFF
+ k) b5 A. d% T" po TC_APPLICATION_LOGGING=OFF
* z# K! M( G7 Ro 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
o 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.
o If none then make best use of software-based Web server and FMS WAN acceleration settings. (i.e. http compression & FMS compression)
; @9 E3 _7 J. y7 [• Optimize OS network settings
o OOTB settings are insufficient
o Applies to both servers and clients
0 G# L/ P% f1 k( L; O/ zo Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
% P4 F3 b2 }( I6 G, U$ aRecommended Server Changes (Windows)
6 S; ?; o& p" O+ I- J9 o' E3 B: FSee Presentation.
/ s! Y& R$ Z: N# p3 O5 r1 f3 l4 |/ ^Recommended Client Changes (Windows)
See Presentation.
9 U6 s! M0 U% O6 BPerformance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
7 M* U& x4 o  [; i; E$ j) t5 o• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
8 W& U9 e% Y+ H4 r• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
2 v- R" y2 \1 A! p9 C8 y: j• Sysinternals Suite (free from Microsoft web site)
. R: K+ L1 N3 U3 b. ~• http://technet.microsoft.com/en-us/sysinternals/bb842062
; w$ ]' f9 T5 u' c3 H2 {Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
$ ~9 i, `5 T4 _0 bo JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
% z- i$ O( U/ X8 j/ b  do Teamcenter System Performance Analysis
3 V" U0 Q' [0 L7 U% \$ V, m• Oracle documentation & web sites
! d  W0 l# u- g8 q• MS SQL Server documentation in addition to:
1 J1 |% p. c% w0 p# J( Co 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
. k( X; p  G9 ^; b* y6 oo Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
 http://blogs.technet.com/b/sql_server_isv/p/siemens-teamcenter-sql-server-resource-page.aspx
% O5 B4 h+ j' u' a2 u; y9 @0 z) F• 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
" ~" J& c8 o" {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

xiefeixiang

调优厉害啊

a150159

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