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

5 z+ @1 r* B  m6 a  ]$ l$ ETeamcenter is Slow! Teamcenter Performance Bottlenecks & Mitigation
$ Y9 G; N4 [, [( }" G
7 [6 u# |, S5 i2 GLarry 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
For those unwilling to join the TcUA SIG to view it, I wrote an abbreviated version here:
Why Performance Matters
, X1 ?; R0 ?0 T• Productivity – doing more work with less
o Improve end user productivity
) \" H6 U0 j+ ?0 l8 Y9 X. Zo Improves administrator productivity
 fewer help desk calls responding to or fixing preventable problems
+ D+ l$ T3 p* W' ?. P• Reliability
; s$ e! Q% d2 a# S; _; So A well tuned Teamcenter environment also improves system stability and uptime.
o Less opportunity for data corruption
; T& M1 O6 i* H5 q5 H5 no Fewer operational errors/problems
• Cost Savings
) w" N9 M- j1 t' p6 ?o Less waiting means less time wasted.
6 U7 |% _; a* Z. |* ?Quick Case Study: Company ‘S’
: i; ~; X; d% L, y, O9 fPerformance 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
: R: ~3 j% \" Q. L+ u" t' iCommon Performance Bottleneck Causes
3 K# U  j  L7 {9 JUsing OOTB settings — OOTB settings are intended for development environments; not production environments.
' r0 S  L1 H# N5 N" P( G  j- z7 y2 E: MOverloaded 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.
• DBAs at companies generally don’t do performance monitoring and tuning of your Teamcenter DB.
" n1 U% c4 j$ K* O3 X) P% t• It’s typically the last place that Teamcenter administrators look for performance issues rather than the first.
, T6 \. u) U8 s% D: E+ }( MMitigating Database Server Bottlenecks
• Must use dedicated DB server
5 h$ M- H1 Y! U3 S9 Z% t# Eo Do not use your DB server for anything other than your Teamcenter production database. This includes not serving additional databases from the same server.
! S7 C* ^3 c* j0 g• 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.
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.
0 h: z, F) q0 m- t( \+ c- Yo Use multiple disk controllers if possible.
• Cram the RAM
# e, v  C% O% {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
% ?5 J9 U# |8 ~& ^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.
2 [$ T1 u& p/ o; Z• Use a good quality network adapter(s)
6 E/ e8 f" y. To Often overlooked as potential source of bottleneck (e.g. packets/sec limitations). Consider multiple NICs “trunked” for better throughput.
4 o+ h' K- i; y8 k. u) j' U• DB maintenance tasks
o Update statistics and rebuild indexes regularly.
* y0 {. _) U0 Y2 oCommon Teamcenter Server Bottleneck Causes
• Overloaded Tc Servers
) m$ n, R0 U9 P# o" G$ {• Poor Web Tier Configuration
• Poor FMS Configuration
7 X: B2 o8 f5 R0 {• Debugging Turned ON
$ f4 S$ ?- H4 r& v- m• Rich Client using OOTB settings
" X" Z% [+ k: M0 m; I- l‘Unload’ Overloaded Teamcenter Servers
" l/ _* f3 y4 Q- L5 u9 a+ [• 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:
5 ^% v; ~/ a, ?2 K/ oo 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.).
6 w7 Z/ O0 j0 N9 Oo Set up multiple FSC cache servers to take load off busy volume servers/storage.
Web Tier Configuration
• Do not use port 80 or 8080
& p9 F: w' l+ ?9 |# [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.
5 S7 L2 E8 m. ^2 `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
• Data improperly routed
& ~6 B) o; p( l, x( \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
o For development purposes only, remember?
* D  f  ^* B) [5 u" D$ K: c• Missing client IP address subnets
• No load balancing
+ ~' F/ G6 ]8 R6 z3 L• Not using remote cache servers for WAN users
% C: K! C+ v# e9 \: i7 a8 a• Not using remote volume servers for WAN users
( l! F4 P8 L: z( n, @0 CFMS Configuration
, |) S' i$ H7 k$ }/ {• 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.
& \: C6 \# H" lo Use correct transport algorithms for LAN and WAN users.
• Tune FSC/FCC cache settings
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
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
: R3 x: J2 K7 g2 K3 ko Use “front-end” FSC cache servers to reduce load on Volume servers. (Requires disabling of FSC direct routing)
) Y! f% u+ a* A0 h/ g  c- ~0 Wo 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 K" G& d! R9 V0 [• 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)
- v! [; S3 p# r3 `8 J! mo 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.
& \3 D5 ~$ v7 N+ x5 v7 PMisc Teamcenter Changes
+ [/ C  D( x  G) l" y2 M• Disable logging and other debugging tools.  Turn them on only when needed. Examples,
o TC_SECURITY_LOGGING=OFF
o TC_APPLICATION_LOGGING=OFF
$ d- C1 c1 R2 E* _/ @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
$ \/ f$ S! e0 Co Improve startup time by having FCC and Tc files pre-loaded at OS login.
/ w* v& j& @$ W5 h9 h" cNetwork Performance
• Use a hardware-based WAN accelerator if using Teamcenter between multiple facilities over a WAN.
7 L3 m8 i3 ^4 o9 K9 s1 fo 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
o OOTB settings are insufficient
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)
See Presentation.
4 V# P2 \# S2 JRecommended Client Changes (Windows)
1 e' K) \9 ^* I9 u% N8 eSee Presentation.
6 I9 b9 `- E4 h) TPerformance Monitoring Tools
• Some useful performance monitoring tools:
• Performance Monitor (comes with Windows)
• Used to monitor OS, Teamcenter, and SQL use of resources
  i$ }& m) d9 I+ ]6 |• Wireshark (freeware network packet sniffer)
• Used to help identify network TCP performance between computers.
& w9 E8 @# p; }) }/ }. u, N• Available at http://www.wireshark.org/
2 \3 D8 }0 S2 u' F• Sysinternals Suite (free from Microsoft web site)
; `7 t. N& E- z0 L• http://technet.microsoft.com/en-us/sysinternals/bb842062
Reference Materials
6 ^$ x4 `9 j, \0 Z• Available on GTAC Web Site @ http://support.industrysoftware.automation.siemens.com/docs/teamcenter/
( O6 D( O1 i4 u+ Ao Teamcenter Deployment Guide
( @; N. C9 y( R- ?o Teamcenter Network Performance Tuning
o JBoss 4.2.2 Installation & Tuning Guide
o Optimizing Teamcenter Client Performance
o Teamcenter System Performance Analysis
• Oracle documentation & web sites
• MS SQL Server documentation in addition to:
! c1 c9 z' R  e% |9 Y  Y4 @o Best Practices for Running Siemens Teamcenter on SQL Server
6 R9 a7 b5 T  N: N 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
! m& W( [# Y6 I+ g 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,
$ M9 q: i2 v5 D% I9 B$ Mo Teamcenter 4-Tier Deployment – Best Practices
o Teamcenter – Database Performance
6 M' c1 G. |/ q! ~7 h6 Co JBoss Optimization for Teamcenter
" G9 b- c7 V2 c$ R- z( ~o Optimizing Teamcenter Client Performance
o Teamcenter Database Server Configuration & Tuning
Contact Information
# ]4 w* M& e: c5 _) ~Larry Carpenter P.E.,  PLM World Teamcenter SIG Chair,  tcua@plmworld.org
/ ~2 m/ g9 `* vTeamcenter UA SIG:  http://www.plmworld.org/TC_UA
LinkedIn:  http://www.linkedin.com/pub/larry-carpenter-pe/44/5b8/aaa
Alternate Contact Info: ideas2nx@plmworld.org, larry.carpenter@siemens.com

' \2 j6 J1 L# I0 O  e, z" ~

xiefeixiang

调优厉害啊

a150159

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