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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
) z5 I1 h) m+ O, }+ e) Ihttp://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf

- K+ `& B1 Z: M$ G  [; uTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
: d3 h& Q: f2 N5 `- x0 [9 S6 a
Larry Carpenter
' k7 ?3 W4 I% W" N0 AAt 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:
0 L/ G! O4 _3 o+ TWhy Performance Matters
• Productivity – doing more work with less
6 c! W  h: e8 n& go Improve end user productivity
- V$ S/ j5 m8 Io Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
• Reliability
3 b) i  S6 R2 ~) To A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
o Fewer operational errors/problems
• Cost Savings
" a; {  L$ }7 q; }- B+ l* a6 go Less waiting means less time wasted.
Quick Case Study: Company ‘S’
+ G  i/ T- }! `6 g2 A# y9 H; DPerformance 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.
2 X( M8 m% V+ d' @* L- `' h  ZSee 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
  ]2 L% r9 r& p) ^+ v* Y+ fCommon Performance Bottleneck Causes
Using OOTB settings — OOTB settings are intended for development environments; not production environments.
  g5 p' n  K* J3 {9 X$ eOverloaded 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.
Databases – The Most Likely Culprit
• Database performance is highly sensitive to hardware, software, and DB configuration.
2 Y& R. B1 D+ X2 S8 m• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
5 r: m, x8 y7 j" x% j: t, X• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
Mitigating Database Server Bottlenecks
* h$ X4 X6 H- v7 _& T• Must use dedicated DB server
( g4 Y2 S$ O3 `( Z) Mo 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.
" J/ u/ ^4 N! A5 v  h! u0 J0 ^# jo 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.
o Use disk controllers with a battery/flash backed cache.
o 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.
• Use 64-bit OS & DB software
: G: Y( S- `- `* ?. Uo 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' K9 ]# s& `6 F& I# N• 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
1 O2 R0 |; B! J# io Update statistics and rebuild indexes regularly.
Common Teamcenter Server Bottleneck Causes
6 e3 a  H5 ~8 d0 L• Overloaded Tc Servers
; H+ z" C$ v! F+ s• Poor Web Tier Configuration
+ q  I+ b% C% w9 @+ o: a• Poor FMS Configuration
• Debugging Turned ON
1 e+ n1 |( m& i$ f3 h• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
+ ~3 {) Z8 Q8 X" |0 u• Put Dispatcher modules on separate computers away from other Tc Servers.
0 W/ Z7 V8 H0 _/ N: V5 s8 P$ G% F• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
  \0 l% p, a4 U4 E* Y- H• 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.
" g: u% M$ k4 Y3 y/ VWeb 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.
0 L# V+ O# k1 O• Enable http compression if not using WAN acceleration
o Must be done on both web server and on clients to take effect.
! D- i4 p" x0 u4 o• Change/tune OOTB settings for Web Server/App
. H- \2 N1 h; Z& E( J0 b- q; Vo E.g. timeout values, max # of threads, Java memory, etc.
$ e) B8 q! l* E' a/ Q6 s8 }o Read tuning guides specific to your chosen web server/app
• Scale it up or sideways
7 K- A& J, R" g, B& |. o7 |9 m0 Uo Add another web tier server, or increase # of work processes (e.g. Web Garden mode for IIS).
, i/ M3 G0 L- S3 |9 Z* q  cCommon FMS Bottleneck Causes
/ i4 y3 G; d0 ?! m! i• 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
; p9 T8 V. K9 G/ Vo For development purposes only, remember?
& c7 P! l1 y) L, K5 T6 h! h• Missing client IP address subnets
( t: l& u9 a% f$ J$ }% a: E6 [- C4 H• No load balancing
' s+ N! S  n" n• Not using remote cache servers for WAN users
# X0 F! {( s" F. S• Not using remote volume servers for WAN users
FMS Configuration
• Ensure routing is correct
; a) N( D. Q2 H; l: o7 vo Between multiple FSC groups via entry/exit/link parameters
2 K- ^# }9 B  `; n5 ko Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
: H" y2 s' \" J- Ko Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
* _* x7 o/ `  z( ^4 \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
+ |) a% E9 J- S( f7 _, A& p3 Uo Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
6 i9 k5 U: ~5 r/ D0 U2 io Place client maps in the closest FSC group to their location.
! e( n9 C6 z+ U• Use multiple FSCs for load balancing
; @" a1 b- x, H1 I. v; ro 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
' P# _) L$ B5 U4 X) p8 D& Ko Greatly improves read performance (load time) over a WAN for groups consuming shared data.
• 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)
7 r" J9 G. l5 w8 A0 Y) C3 ]o Greatly improve write performance (save time) over a WAN especially for CAD data.
9 k* R0 ]) O! o3 q" r( C% u• Prepopulate FSC caches
7 b7 v3 ], o4 no Run a nightly script to prepopulate shared data across FSC caches.
+ e( W# s5 n: H4 _- R$ {Misc Teamcenter Changes
4 E6 M2 r! V. V, Z• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
, A" g  ^9 S4 _) P' k4 ]6 Qo TC_APPLICATION_LOGGING=OFF
o 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.
% }0 v, Q' `6 Z, {' B7 m, ^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)
) N3 w# ]0 [$ r• Optimize OS network settings
/ l* n# s& F$ b  u  ?. q0 {) po OOTB settings are insufficient
o Applies to both servers and clients
1 e) O, M# a% n8 ko Examples, increasing # of tcp ports, disabling NAGLE algorithm, increasing buffer sizes, trunking multiple NICs, enabling Compound TCP, Large Windows Scaling
; O1 f, A  {' oRecommended Server Changes (Windows)
$ x! m  Y. V& Q: bSee Presentation.
Recommended Client Changes (Windows)
# e2 [) p/ K8 P; J6 gSee Presentation.
Performance Monitoring Tools
• Some useful performance monitoring tools:
. r" v+ z+ h1 Q% @, J3 G: Q0 T, ]• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
' I+ r" Y2 c. \• Used to help identify network TCP performance between computers.
. j5 R; B. z: }7 z+ D( O: Q• Available at http://www.wireshark.org/
5 A, |8 H. s$ X) v. P& F+ Z8 R• Sysinternals Suite (free from Microsoft web site)
3 x* }9 ?# G. f5 }1 I. L0 L• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
- U- z7 p) h9 ?1 S  B• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
% I3 k; a: U8 o( B6 m; Xo Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
/ R& h/ ]; c/ b- ~, Z; H+ Y+ ko Optimizing Teamcenter Client Performance
' P7 B% Z% [4 q! N4 g7 mo Teamcenter System Performance Analysis
$ i; J  g% j) |- P# O5 f• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
o Best Practices for Running Siemens Teamcenter on SQL Server
" z9 e! S& j2 `% n: l7 |' H http://download.microsoft.com/download/7/3/6/7365D2BB-BB34-4D28-A128-F2C8FBA6E995/Siemens-Teamcenter-and-SQL-Server-Best-Practices.pdf
6 R+ t" ~: }; O" Lo 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
% f9 U' I5 Z/ e  Z7 Y4 R; o• Past PLM World Conference Presentations available at www.plmworld.org,
o Teamcenter 4-Tier Deployment – Best Practices
; O  [8 ~7 F. Q9 L7 ]o Teamcenter – Database Performance
, f- j, R" l3 q. ?o JBoss Optimization for Teamcenter
o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
( m8 Q' Y- \# R8 ?1 @% E% ~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
, z$ ?0 n' \! v" e) }Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
4 g7 [9 H9 Q) r1 B1 _( U' [
$ `/ B) E3 r, i2 W7 [

xiefeixiang

调优厉害啊

a150159

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