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

admin

http://www-cad.fnal.gov/PLMWorld2008/Teamcenter%20Unified/The%2520Network%2520is%2520Slow!.pdf
http://www.plmworld.org/p/bl/et/blogid=43&blogaid=218
https://support.industrysoftware.automation.siemens.com/docs/teamcenter/Network_Performance_Tuning_V6.6.pdf
) R( a3 x6 o3 F# m/ z7 |' K. R' y3 r
4 P; J1 W, F; l: |8 UTeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
& K5 r3 s1 o, L. g. G  x  n* a) s3 C
* B6 X3 A+ R' S$ ^Larry Carpenter
At 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
. L  @) z, a# K& A" _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
8 t" ?: j# m+ f& R; w% yo Improve end user productivity
o Improves administrator productivity
) B, G+ {: V- @6 B' K1 w5 H fewer help desk calls responding to or fixing preventable problems
• Reliability
. Y, D# @0 n8 F8 |; z  `, l' Uo A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
& C5 u' f+ N) e: j/ Xo Fewer operational errors/problems
; H' m; }1 R) R* V+ o• Cost Savings
o Less waiting means less time wasted.
Quick Case Study: Company ‘S’
# O9 L% H) O7 j! g2 O2 m4 iPerformance 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.
Overloaded servers — Putting too much on a single server.
4 U: ^. f! h7 r) cOperating system settings — Network settings most common (e.g. TCP parameters).
3 @% \7 [4 D, n- A) BLack 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.
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
, _) x0 e: u# }7 M6 U: R* j• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
$ v& Y) T; v7 F5 b% G; Y2 k( kMitigating Database Server Bottlenecks
6 @2 E% C, v8 K  Z• Must use dedicated DB server
  [+ [4 i/ W% w! j3 n9 _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.
8 |- a( y# p9 H• Must have fast dedicated storage for DB files
( p0 `, z# P( z8 Q, b  e7 Lo 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.
+ |7 k. C8 r0 `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.
* i  ^8 j) g- P4 ^• 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
% u$ S! z& s' w5 }2 g/ U, c5 A6 Ko 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.
- ?- m/ N9 Y& }) K• 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 k& \7 v% n; G# c& Po Update statistics and rebuild indexes regularly.
  I' x4 T: t8 ?# q6 e$ ~. S1 B. mCommon Teamcenter Server Bottleneck Causes
. H$ _1 q! M2 Z6 ?/ M• Overloaded Tc Servers
; p. n) i" i  S3 T: o7 l• Poor Web Tier Configuration
• Poor FMS Configuration
4 G0 A! _% c' e7 x, a• Debugging Turned ON
$ a) L; K1 ~  n& F# {; @( g• Rich Client using OOTB settings
‘Unload’ Overloaded Teamcenter Servers
/ K+ l/ [1 U. l3 O5 O* ^" u• Put Dispatcher modules on separate computers away from other Tc Servers.
% f: c1 O. k2 B! D& V• Separate the Web & Enterprise tiers from the Tc Corporate and Volume servers.
; g1 s5 c6 W# }/ v5 S! b" b5 N. N• Use load balancing for Middle Tier & FMS:
. Y0 t- D7 [: Wo 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.
Web Tier Configuration
3 V- D6 Q5 q$ A3 L• 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
o E.g. timeout values, max # of threads, Java memory, etc.
o Read tuning guides specific to your chosen web server/app
* V" l- I. f' z7 J; k+ c• 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 k. Q# H3 q" S. X• Data improperly routed
, T1 N" L2 c8 s3 c/ ^/ n7 f& do 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
  k' M' }4 |( X2 U0 r" l( |o For development purposes only, remember?
- y" B; m7 ?9 s: u& e• Missing client IP address subnets
• No load balancing
! r) i) h: g: z" C1 q• 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
- K; }' ~$ A+ \- b1 d# j0 N+ `o Between clients and their assigned FSC servers by using complete and accurate ‘clientmap’ parameters for ALL clients.
; U7 P9 u$ [: U& k; s+ ^o Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
7 J7 ?+ S0 N3 j* Z5 ~o Simply picking a total read/write cache size is not enough.
/ z; c( R5 }6 a2 [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
7 j- F. l/ N- y3 t( m. Zo Determine ALL potential client IP address ranges and where they are located. Don’t forget to account for VPN IP addresses.
. }2 H+ V- z* Y# t8 ro Place client maps in the closest FSC group to their location.
• Use multiple FSCs for load balancing
% c+ @8 c/ F; s0 Z- m; T! ]o Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
. x% s7 M+ u' k- A* M$ bo Use redundant FSC cache servers to load balance each other. Also provides fail-over.
2 y7 \- a% X  v- O( [• Place FSC cache servers close to users
o Greatly improves read performance (load time) over a WAN for groups consuming shared data.
# m* [8 v6 u' d% F• 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)
9 n- R" A% d, K6 D; lo Greatly improve write performance (save time) over a WAN especially for CAD data.
• Prepopulate FSC caches
o Run a nightly script to prepopulate shared data across FSC caches.
+ ?7 R( K  k/ f8 t) W; cMisc Teamcenter Changes
2 o7 Y. [5 e5 _! l8 f5 `/ t• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
( W5 z2 X- s) _) zo TC_APPLICATION_LOGGING=OFF
8 _  N  g2 T! @# Q+ s4 \o TC_SLOW_SQL=-1
• Rich Client ‘Teamcenter.ini’ configuration:
7 F8 z: d; h0 `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).
% q9 u! q7 k( |: k0 N4 u• Enable FCC File Warming
o Improve startup time by having FCC and Tc files pre-loaded at OS login.
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)
- D- s) x0 n  d1 D( o/ }• Optimize OS network settings
o OOTB settings are insufficient
& k- T9 h0 m4 V/ V4 To 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
" k% K- `' y: ?; ~; uRecommended Server Changes (Windows)
$ a8 O  K  W9 O1 ?See Presentation.
Recommended Client Changes (Windows)
7 \! ]7 @  e3 p* V  E* x6 gSee Presentation.
+ \# {3 s. y9 yPerformance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
5 Z9 C3 F1 u. [4 u4 V& H• Available at http://www.wireshark.org/
- I8 c- {! ^1 _4 t8 g8 z) b• Sysinternals Suite (free from Microsoft web site)
1 G5 M; n" y! Z7 n• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
o Teamcenter Deployment Guide
o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
. ]' }" m2 n& V% A+ n  s$ ro Teamcenter System Performance Analysis
• Oracle documentation & web sites
3 @; t' S6 D2 T9 h5 m• MS SQL Server documentation in addition to:
" A% P" ~* ~( U* W; t$ \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
) O5 s$ z/ {. {1 oo Siemens Blog on Technet
6 t2 O( X7 m$ J 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
8 V% y" s( p9 H. w3 q2 i1 `o JBoss Optimization for Teamcenter
3 H% d" k% V5 o1 To Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
$ Q) K( q& _3 g* U$ r3 x0 f  a1 UContact Information
+ G. C* t& A5 E3 b6 `# ^4 u# q$ eLarry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
Teamcenter UA SIG:  http://www.plmworld.org/TC_UA
+ T5 |& e- o6 ULinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com
; H3 c  F) n2 m4 Y$ d. ^! f9 e- j

xiefeixiang

调优厉害啊

a150159

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