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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
' f; U; I4 E- Q  nhttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
2 m9 h2 c' x0 F; Ihttps://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

" @- [4 ~, }4 J# o# o. K; iTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
6 ~- H9 a  F! `) L5 p2 u- W
, P& c) N+ O. n) SLarry Carpenter
* n7 H& W/ f, e4 ~2 a8 Q( gAt 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:
7 L4 S+ w2 `% tWhy Performance Matters
1 I4 E# c: R5 |* q3 N8 l4 V: v• Productivity – doing more work with less
0 j2 m) `9 H7 _. S! [6 to Improve end user productivity
/ Q. f# g- G9 @: B7 a" So Improves administrator productivity
. B" H% X$ p2 @) s7 D8 n; z% } fewer help desk calls responding to or fixing preventable problems
$ Y" F6 _& Z6 j; q- ], l• Reliability
o A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
/ z$ m; s6 h* K$ R" t. N% ao Fewer operational errors/problems
' m( V# B2 U4 b• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
* R( B1 Q+ O$ r# `$ BPerformance 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.
5 e% x* O* w+ zSee my March 2012 article on PLM World’s website for details:
' |8 }' G& j6 W1 u) b% D- P, zTeamcenter Performance – Hard-Earned Lessons:  http://www.plmworld.org/p/bl/ar/blogaid=152
4 [- l) j# o: f; F7 ~Common Performance Bottleneck Causes
- L( q+ e1 j9 u2 ?4 oUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
3 S1 v; T1 N8 C6 S" _1 qOverloaded servers — Putting too much on a single server.
! ~2 l7 }( v/ b5 |9 b! v& EOperating system settings — Network settings most common (e.g. TCP parameters).
6 f3 V6 A( j& a0 }+ z% u3 C. U3 @Lack of performance monitoring & tuning — Performance doesn’t improve all by itself. It requires human intervention to determine root cause and address it.
2 V! r6 u' r; V$ P& w$ X1 CDatabases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
3 O% J# t& i: c4 K% M, O+ K• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
  u6 a( f( g8 u/ D• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating 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.
% v7 Y3 B+ }9 \& B5 m, P: {• 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.
2 F$ G5 f5 k$ s# [7 ^4 Fo Split DB data, temp, and log files across those RAID partitions according to DB vendor & SPLM recommendations.
o Use disk controllers with a battery/flash backed cache.
/ e5 i  U5 n1 ^& ?7 ^/ B' s) go Use multiple disk controllers if possible.
• Cram the RAM
; r2 \, V# a% qo Ideally should be greater than the database size or in-memory footprint. Otherwise disk swapping/paging will occur.
• Use 64-bit OS & DB software
" c- M' z  c0 M- z# jo 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)
" r, O9 w5 }- ^5 ?! w1 |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.
; v+ ~. z3 ?: JCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
• Poor Web Tier Configuration
# y, |/ Q& B9 A• Poor FMS Configuration
• Debugging Turned ON
  |5 d$ o, R1 @( ?• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
! f* S! y" r9 E1 ^+ O! y• Put Dispatcher modules on separate computers away from other Tc Servers.
• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
0 B1 u& O9 v: [9 |+ `• Use load balancing for Middle Tier & FMS:
4 t  c- z6 C$ f3 K2 ?% u2 ko 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.
3 F2 n, g! F" f  C% QWeb Tier Configuration
/ h8 |/ a! O1 N8 x+ @! O/ q• 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.
; P% P* F( y2 q1 ~& j+ r5 F0 Z• 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
o Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
Common FMS Bottleneck Causes
8 k3 Q$ _4 q$ Q: A( O, b1 q: h5 ^• Data improperly routed
6 e" n+ ]. b- L( Z- F6 Lo 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?
• 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
• Ensure routing is correct
o Between multiple FSC groups via entry/exit/link parameters
2 p5 x& g' t" I; W1 to 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.
" x' M5 t$ r4 J- d, {% R• Tune FSC/FCC cache settings
1 ?  `  H) A# R; c$ z6 zo 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
3 y4 i/ U7 Y3 s5 Y0 D: ao Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
* `8 R. q% e) r) h) {, ^% `& Do Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
5 _# @6 U0 H2 A* go 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.
( |. B9 v; l2 L# i  ]+ ~• Place FSC cache servers close to users
7 |+ H* O) F" ~* ko Greatly improves read performance (load time) over a WAN for groups consuming shared data.
* ?/ J4 }8 K  B' f9 {- `• Place Volume servers close to users
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.
; |* B: B, B5 Z, L/ x• Prepopulate FSC caches
* T5 _7 y) }, So Run a nightly script to prepopulate shared data across FSC caches.
  t8 |; @9 I* ?9 W# P7 `5 EMisc Teamcenter Changes
5 |4 o. Q; j' ~; o9 U  H! P& M• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
7 S6 o* c- y, h9 e) h  go TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
o TC_SLOW_SQL=-1
! j. F3 W; G% o& M9 ^& W7 E• Rich Client ‘Teamcenter.ini’ configuration:
6 ?, H% A3 G- A0 `" co Modify Teamcenter.ini file to increase Java Memory and other settings. Will improve performance/stability when perform large operations (CAD, PSE expansion, large Workflows).
7 `' J- Q% R- L: E  }/ H) p: P  w' s( w• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
Network Performance
$ T' }; O) n; V: u6 @8 o• 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)
; h; L% c& v; F, Q# b+ z• Optimize OS network settings
o OOTB settings are insufficient
o Applies to both servers and clients
4 ?4 t9 }! L4 z5 H1 v% to Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
' c( ~' |3 x* I7 h0 F* _Recommended Server Changes (Windows)
See Presentation.
Recommended Client Changes (Windows)
See Presentation.
# _4 g2 B% d- A$ E  \$ A) EPerformance Monitoring Tools
" u! t6 C4 R! L. X% M: s3 U* h9 V• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
% \# E) C9 G3 V' v0 o- H/ Z# F• Wireshark (freeware network packet sniffer)
% S2 x# Z  K. J7 O8 ]/ ^• Used to help identify network TCP performance between computers.
• Available at http://www.wireshark.org/
. g: y; w: `5 ?9 M  {' k• Sysinternals Suite (free from Microsoft web site)
• http://technet.microsoft.com/en-us/sysinternals/bb842062
% x  n$ V$ l9 }& EReference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
2 s* O' y' M( ]1 I# Ro JBoss 4.2.2 Installation & Tuning Guide
( H: r6 C) b. @0 o$ oo Optimizing Teamcenter Client Performance
# M+ f9 D: V; O$ e, Go Teamcenter System Performance Analysis
/ ^7 A" n1 P; W1 {) q4 K• Oracle documentation & web sites
, K1 a' W6 H' `- \6 u: p/ p  P• MS SQL Server documentation in addition to:
" D4 O# m; h8 h: p9 U: W8 Io 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
: l9 t/ v' E; y+ Z http://blogs.technet.com/b/sql_server_isv/archive/tags/siemens/
$ I2 g1 U/ C/ _7 Z& W7 fo 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,
% q/ Q' x4 S* o0 ?: U, Uo Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
6 `' K4 \! R/ R1 g& m' WContact Information
Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
. i7 Q/ c6 e7 S; G0 vTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
) {* @: \+ o7 s& Y+ XLinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
- n; |  O7 t4 QAlternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
3 |+ V; u! R% }
, n2 X+ C9 }8 p: z& l, i1 A( B

xiefeixiang

调优厉害啊

a150159

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