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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
& G9 Z- W/ `  f, e* j) Ihttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
! u) o) I$ T: Y8 nhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

! ?1 m# L* q  \, BTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation

Larry Carpenter
5 L  n% R) @" CAt 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
0 u& Z1 g, H; T& K1 m: @o Improve end user productivity
9 i! r4 b; j* m' _8 ]2 L  vo Improves administrator productivity
% v* I/ P* [" R 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
o Fewer operational errors/problems
• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
2 N3 f/ r* j$ x" c$ b; ]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.
, k+ z0 M* E; Z7 D0 bSee my March 2012 article on PLM World’s website for details:
4 w$ ^  o$ w2 T4 i) KTeamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
, Y8 t1 K- l. f( I- I# u! m$ mOverloaded 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.
# L: `/ W$ z7 r, A* oDatabases – The Most Likely Culprit
7 ?" ~, p: x5 g' U2 M• Database performance is highly sensitive to hardware, software, and DB configuration.
- }  W7 d5 @3 }  j$ Z- W. p/ r• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
4 q# q/ K: x* `: n+ Q! r• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
% m6 y8 J* v# d* B2 [• Must use dedicated DB server
8 I$ ~0 t( w1 Q' ko Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
, s5 j6 p) H* [0 S• 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.
o Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
' A& [" c/ ^: h& Z4 c. l: mo Use disk controllers with a battery/flash backed cache.
o Use multiple disk controllers if possible.
• Cram the RAM
9 X- |0 f" ~9 R5 w$ m: fo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
% v0 b2 b: K7 ^+ [, T4 O• 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)
. c/ s3 t. z7 \" vo Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
3 D6 ^7 h; S0 @• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
. ~2 e) O( a  F# ECommon Teamcenter Server Bottleneck Causes
, i4 |' `+ [8 ^" }• Overloaded Tc Servers
! p# V2 B" O. y  Z0 G) Z& o• Poor Web Tier Configuration
• Poor FMS Configuration
• Debugging Turned ON
• Rich Client using OOTB settings
! F& k- c% c# y/ A8 ^‘Unload’ Overloaded Teamcenter Servers
, z, C& G* I$ x. @• 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:
" X8 E* A! f4 o) Eo 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.
& s2 K  L8 P) k. U8 Z. }Web Tier Configuration
0 A$ h2 a' f! G$ x1 Q2 p- S, d9 v- y• Do not use port 80 or 8080
3 D$ X% x8 x: J1 q3 Q  F$ g; Fo 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
  m( @* h% I! w6 U4 C6 n5 io Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
o E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
* N& _0 M2 `2 g; ao Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
• Data improperly routed
1 ~2 `* c' E, F  I- t2 j& Xo 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
) v6 A4 w. |3 ]2 [1 _o For development purposes only, remember?
• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
FMS Configuration
9 p4 y7 O, w+ O$ Z' i• Ensure routing is correct
$ X9 ^% D, G" Q6 x" Y5 I  k+ ro 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
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
• Ensure correct client maps
% \' v8 }! N. fo Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
" E  U) T: ]% Co 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)
+ m1 L3 k& {/ p6 ko Use redundant FSC cache servers to load balance each other. Also provides fail-over.
9 b' \  N# A' \+ x7 s, {! [• 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
) f9 A: c( B7 K8 }0 V1 m3 Ho Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
7 o3 j! `; @8 a" s! I% x, Q3 So Greatly improve write performance (save time) over a WAN especially for CAD data.
: _" }/ Q+ q5 L6 Z! P7 ]' ^• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
. _: D, Z( N  z0 W- q7 J& Q) Y6 AMisc Teamcenter Changes
8 }; e+ @4 e! w4 P# x0 a• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
$ F6 X, M% r0 _( q0 g3 [# Ao TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
* q  s* G. m3 c& S# M• Rich Client ‘Teamcenter.ini’ configuration:
" t8 B2 z3 a  b: Ro 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.
. U9 R8 s* W; u. r% p* b/ Y0 K$ ^' {# nNetwork Performance
' ?* ?  X: P! N$ p/ F9 C; ~• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
0 h$ S7 Z" I! A& u1 H0 i6 j; ?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
% r: f. e  v% L7 N' W! |6 lo OOTB settings are insufficient
o Applies to both servers and clients
8 H; Q/ t' h9 z+ V' uo 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.
7 p; ]! p7 T0 _) k" _8 n& ^+ cRecommended Client Changes (Windows)
See Presentation.
Performance Monitoring Tools
- h! o' z; r' C% C7 [9 U• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
( ~# o. r/ V2 f6 R7 G( v( v4 {• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
+ D1 H# p2 Q: a8 Z• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
; ~- X* Y+ G6 h" Y• Sysinternals Suite (free from Microsoft web site)
/ @* Z0 j" Y- H: ?5 G• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
! L4 w# [% w" u8 u9 n7 |o Teamcenter Deployment Guide
2 R$ }! Q" x* Uo Teamcenter Network Performance Tuning
7 g0 e' A9 I& B) to JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
$ l+ k# f" g6 g) d# Jo Teamcenter System Performance Analysis
& z; q* B  Y: ~- V• 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
, D3 O5 ^. Z. S, [: }) ho Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
! }: ?0 R* z  Q0 e' `. X  n, O 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,
1 u# Y2 o  F* E0 [2 Uo Teamcenter 4-Tier Deployment – Best Practices
7 b) W+ K, A  T5 To Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
: l: G' c. _6 L- u* R. [* ko Optimizing Teamcenter Client Performance
1 g3 j5 u  g& d8 Eo 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
6 s  R4 ?. g1 C! ULinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
/ P5 T8 Y* }! L) bAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
; g5 ], Y3 p7 H3 _5 r$ }
6 N% ~6 [. D' c& N7 a: b

xiefeixiang

调优厉害啊

a150159

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