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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
7 W& t% o- f0 Z6 x6 Ohttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
" l" I) u6 S5 M7 ~8 Bhttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

Teamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
9 R3 p- u4 H2 A
5 X' e! }. s+ I: jLarry Carpenter
. L" C$ Z  `" F% yAt 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
+ ^; C/ u2 t  ~0 [! @For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
3 Q9 [1 n* @( x" a7 D5 E• Productivity – doing more work with less
7 ]# i# Q  X6 P! x8 q8 E: Zo Improve end user productivity
' o& Y( D6 |! G! [* j! F2 ^o Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
1 F$ F% }. e+ j, [+ ~• Reliability
! Z7 I  n( [0 M* `o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
" C! B$ r! M# h9 e# i$ a) ~# Y• Cost Savings
o Less waiting means less time wasted.
( ~0 n: Z7 f# G! i7 H$ L* ]# ~7 d: UQuick Case Study: Company ‘S’
+ ^5 C( c/ f6 T9 gPerformance 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.
. v( B% F/ Z( C3 u. h. J+ Q1 `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.
Overloaded servers — Putting too much on a single server.
: L9 r3 ~7 U# h# {$ JOperating 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
0 s( c7 M$ f7 v( P• Database performance is highly sensitive to hardware, software, and DB configuration.
, H* c! [: D1 M7 Z6 h+ \9 T• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
" r1 u5 N2 W( S4 Q• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
* `. }, J0 c+ J# g. k/ [$ S0 t0 ^Mitigating Database Server Bottlenecks
, K6 S5 b& }) g! x, T' k• 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.
; G, \1 N% D) e6 l, [* S• Must have fast dedicated storage for DB files
+ c8 u1 s6 W' `0 y* go Avoid using a NAS device; especially a shared NAS. Use DAS (Direct Attached Storage) instead.
# S( A5 |2 Q% xo 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.
$ p8 z2 L5 h+ a7 U" n" q- ?o Use disk controllers with a battery/flash backed cache.
/ Q# Y: v8 ~2 C1 M5 y9 Q# Q* n; ?o Use multiple disk controllers if possible.
• Cram the RAM
/ i+ u. L; Y8 x: \* zo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
: ]- d% f4 D8 _% W; V# b+ r• 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)
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.
6 a% }0 r$ U# O9 G9 C( B* m0 FCommon Teamcenter Server Bottleneck Causes
# m$ R7 \! S0 f3 c$ T4 P( d. C5 m• Overloaded Tc Servers
+ J6 G: N# ~) [. h3 v: K% D• Poor Web Tier Configuration
• Poor FMS Configuration
& M" w( }1 ~) o2 |• Debugging Turned ON
. j( z8 x" R% i0 A+ x• Rich Client using OOTB settings
‘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:
4 X( Y& n& G- v0 qo 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.).
0 u3 M) O7 T) o4 }o Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
, E/ `8 K. h0 U7 Z* @• 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
% {8 g) J) R5 ?8 x7 Z- Ho Must be done on both web server and on clients to take effect.
• Change/tune OOTB settings for Web Server/App
! h7 {" ~) M# E* b, \o E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
9 t$ m/ @- o" w' B8 ^; S• Scale it up or sideways
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
9 S0 i5 u  C; {# x" Y8 p! A2 QCommon FMS Bottleneck Causes
• Data improperly routed
8 l4 b# Q5 j% v3 ^# J2 D9 K( Ko 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?
* q! T! q; i3 o5 Y! ^5 E7 U• Missing client IP address subnets
• No load balancing
* R* ^* i  T; f( {& B% w6 U  j( C• Not using remote cache servers for WAN users
• Not using remote volume servers for WAN users
  S, X) Y- G7 O8 K0 T6 b! jFMS Configuration
& ?& O; }: l' A% h: j• Ensure routing is correct
; c3 E' j- e2 F7 S# K. F- Ko Between multiple FSC groups via entry/exit/link parameters
) _- s8 L# J8 ]* Wo Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
  c" l! r5 g: w* j+ V! xo Use correct transport algorithms for LAN and WAN users.
, {8 K5 {; o5 f+ i" O• Tune FSC/FCC cache settings
o Simply picking a total read/write cache size is not enough.
; t. r; J' a0 e- o0 a5 Do 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
; A: e; _6 \1 X8 _  K" }9 x5 B• 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.
# I3 f$ z, A) jo Place client maps in the closest FSC group to their location.
9 g3 s2 S6 C/ e. h8 A& N/ l• 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)
! d: S+ q! T& b6 r6 @8 n1 W: do 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.
* A# \& L/ H6 Z! n! I& p: G• Place Volume servers close to users
1 q" |" }) I  V4 u* `o Use Store & Forward or at least place remote volumes near remote users. (Backups of remote volumes are critical)
  S8 P4 ~/ m& N9 @o Greatly improve write performance (save time) over a WAN especially for CAD data.
) Q& C5 n" T. o# [6 Q• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
Misc Teamcenter Changes
( Z) m- H$ e' x: _: }+ W• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
  z, E; w4 i9 m" \o TC_SLOW_SQL=-1
, z$ S( \! r% J' }' k/ _* m• Rich Client ‘Teamcenter.ini’ configuration:
6 B* h  o8 c: [$ ~6 o$ }) ~9 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).
• Enable FCC File Warming
$ t, u' |  F% \: Io Improve startup time by having FCC and Tc files pre-loaded at OS login.
* v9 ?/ B, v2 g5 H- WNetwork 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
3 F& z2 y4 C& E3 b& v/ @o OOTB settings are insufficient
) }0 b% E* j7 C- V& u! y  }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)
1 r: E8 G' ~0 @See Presentation.
1 A$ t& y/ M% G) T6 C* k$ `Recommended Client Changes (Windows)
See Presentation.
0 U$ i& L5 F: H; J6 M) lPerformance Monitoring Tools
• Some useful performance monitoring tools:
, ]7 v- [* c) E- ^0 f$ B• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
% y6 n  }) e& k; H( l1 h0 q4 Q( b7 y• Wireshark (freeware network packet sniffer)
* t4 S  U* W# S& `* O9 g! H7 J• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
• Sysinternals Suite (free from Microsoft web site)
% a* a: y' m/ P• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
* T' t% A. K  _7 f• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
% N3 e! c7 ], M, b! So Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
8 ]7 p5 x" _0 D( Co JBoss 4.2.2 Installation & Tuning Guide
# b, |/ Z9 Y- Po Optimizing Teamcenter Client Performance
4 p3 G) z3 D/ l! j$ i. {6 v0 s7 No Teamcenter System Performance Analysis
* H# m8 w+ E% f• Oracle documentation & web sites
+ `4 E+ G1 ~& w# v- o6 Z4 `+ ^• MS SQL Server documentation in addition to:
# D. x* Z$ n5 h6 z0 [! H8 N! Go Best Practices for Running Siemens Teamcenter on SQL Server
# ~. j- W3 h  S2 o) ~6 o- `3 H6 y 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/
o 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
o Teamcenter – Database Performance
: P2 f' _3 A; J% }' Wo JBoss Optimization for Teamcenter
6 U& P2 d3 Q; J6 eo Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
* D$ `  c' R& n% I; H' SContact 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
+ k1 g6 V# n+ E9 \6 {0 `6 k0 |# lAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

, q( [+ D/ o6 M$ L' s9 J' @

xiefeixiang

调优厉害啊

a150159

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