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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
% s- W& |, E# Ihttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
% J& t' V1 U8 s2 Z3 Q$ J  S0 B; chttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
/ L$ M$ m( k; l
Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
$ O/ C6 ~+ u, [
5 ~% }7 N! z+ R8 w' l9 kLarry Carpenter
' I% o- C& A0 C$ e- @: OAt 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
5 v7 ?; a% B, ~# r! b; b* uo Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
2 T# A+ @- J5 Jo Less opportunity for data corruption
o Fewer operational errors/problems
8 {/ u- k5 w  u9 L; i5 Y• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
: y) ]: ~8 k" z2 w$ ?8 wPerformance 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
Common Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
8 R3 I3 x7 [4 b" }8 o6 POverloaded servers — Putting too much on a single server.
5 d  v( V$ o3 C5 k# G; pOperating 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.
Databases – The Most Likely Culprit
( r( \* ?2 ?9 q7 H; D• Database performance is highly sensitive to hardware, software, and DB configuration.
" f' l1 D9 O( b$ w, f• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
4 T$ @  d6 W1 W! H' P7 u. j• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
1 R, s$ w0 L/ b( c4 k! L• 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
o Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
. T' J6 b3 e, W: c6 J# ]. p; to 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.
3 _. B! Y+ ~% s2 g9 Mo Use disk controllers with a battery/flash backed cache.
8 t# U; A; H1 I9 N; }6 Wo 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.
$ V5 v( ?- q0 T' @- ]2 Y• Use 64-bit OS & DB software
* `8 _! U7 {; l5 mo 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.
& q/ {+ ^- P' R. o• 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.
9 _+ P6 d4 U, B  B* L• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
9 L5 `" K3 F( \) g8 aCommon Teamcenter Server Bottleneck Causes
- }* c1 |0 y& o* W• Overloaded Tc Servers
8 h* I2 q9 M. O# i, U0 n# h# f, O$ [• Poor Web Tier Configuration
! o2 t; S7 ~" t; Z• Poor FMS Configuration
• Debugging Turned ON
+ i& x% F8 \2 [: r$ q- ^1 U# F' t1 d• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
) r5 L) k; e9 i8 c4 q; n" B• Put Dispatcher modules on separate computers away from other Tc Servers.
$ ]1 x' c2 `2 }8 a6 ?3 A• 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  h9 _) E. G5 Zo Set up multiple FSC cache servers to take load off busy volume servers/storage.
0 i9 y  c' ]6 w9 t3 Z% ]; R, \Web Tier Configuration
• 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.
• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
7 S6 C/ `" r0 v" d& To E.g. timeout values, max # of threads, Java memory, etc.
' d* E0 W0 s7 s. \' so Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
/ {* V$ ]3 I' v; h/ F& K4 D6 bo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
# w8 y) g* V4 G8 a7 A/ i$ ~Common FMS Bottleneck Causes
, `( C1 ~% E* L4 R• Data improperly routed
( ~1 Z8 b: M" Q$ C( Co 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.
* Q: s: p- O/ d8 Q1 ?• Using OOTB settings
' G3 k9 d+ Q1 k7 F6 F5 l+ F' T  `o For development purposes only, remember?
9 E  x' H" P/ T  C2 ~3 p2 G% J• Missing client IP address subnets
• No load balancing
• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
( q0 B9 i( C6 `- e1 t" \FMS 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.
' B# ~( C4 t8 ~) I. R• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
% l) s$ L, y0 _# _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.
o Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
6 k7 }1 N7 r# N1 go Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
, u, D4 w  d* t' [3 |- Qo 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.
1 Y! ]/ f2 R6 Y! E4 _• Place Volume servers close to users
( n9 x, y4 J  D3 C% O5 j$ ^! @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
1 g. p, }& R) I; Yo Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
& n* b! |' W. c. S& W+ v# L4 Fo TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
  S0 r3 i; o1 a$ }o TC_SLOW_SQL=-1
5 b2 g% _& w) ]. l* `+ J3 k. A• Rich Client ‘Teamcenter.ini’ configuration:
% u& C  x- N6 _! f  y- 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).
0 x( H- Z7 M! G/ v: P( `• Enable FCC File Warming
2 K  @; c5 `- B; ao Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
* ~1 Q- [, m; B" K• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
8 @% g  K1 V: t" x. Qo 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
: L! {; V' q8 I  A3 p4 So OOTB settings are insufficient
o Applies to both servers and clients
3 L% R" v& J4 K+ P6 ^' ?. }o Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
$ V9 {. \/ @+ |5 lRecommended Server Changes (Windows)
See Presentation.
! w' v: C) ]5 I! N9 s( W+ T' sRecommended Client Changes (Windows)
See Presentation.
) m. n# W6 E* d7 TPerformance Monitoring Tools
, T  G2 _+ m; d( w# I' X• Some useful performance monitoring tools:
6 d( X4 B9 T8 E. Z& Q• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
# h0 k+ U; Y+ \# u• 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
Reference Materials
- H) u3 i1 G$ a6 Z$ V7 M• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
# @0 b" N0 g  {3 j' t+ A. e1 V5 fo Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
' `) ?; ?2 {3 V3 T5 t/ c5 Ao Optimizing Teamcenter Client Performance
/ m: B8 Q1 S9 u* i5 {o Teamcenter System Performance Analysis
% \$ \9 k. p0 C$ L, K  Y6 I4 m• Oracle documentation & web sites
  s4 ?3 n# ~7 H• MS SQL Server documentation in addition to:
) ^/ A- W& z4 P( q; ?o Best Practices for Running Siemens Teamcenter on SQL Server
5 B1 Y+ g1 U/ m# e http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
4 |- \( v9 v3 @* H. B) N! bo Siemens Blog on Technet
 http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
o Siemens-Teamcenter-SQL-Resource-Page
' F* O. N5 _9 b' P 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,
8 f& F  `3 K/ o7 }! vo Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
0 e8 z( [& o" F0 I, I5 [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
7 u4 B# y9 Q; b5 U5 HTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
) y8 |3 W! P: [0 ~5 P8 f' ^; cAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
8 f9 D! o; y; t( P% M; V' T" E) j

xiefeixiang

调优厉害啊

a150159

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