* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download BravePoint 2010 - Midwest User Group
Oracle Database wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Relational model wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Concurrency control wikipedia , lookup
Database model wikipedia , lookup
Versant Object Database wikipedia , lookup
Top Performance Enhancers Top Performance Killers in Progress Dan Foreman Progress Expert [email protected] Introduction Progress User since 1984 (V2) Presenter at many Progress & QAD Conferences Author of: Progress Performance Tuning Guide Progress Database Administration Guide V10 DBA Jumpstart Virtual System Table Guide 2 BravePoint 2010 Introduction – There’s more Developed these tools for DBAs: ProMonitor – Monitor Progress DBs ProCheck – Monitor AppServers, WebSpeed, Admin Server, Name Server, etc. Pro Dump&Load – Dump&Load a Database of any size with nearly no downtime Other stuff 3 BravePoint 2010 Introduction – Who Are You Progress Version V10?, V9?, V8, or ?? Largest Single Database Database Operating System 4 BravePoint 2010 Top Destroyer #1 Ad Hoc & Period Ending reports run against a Production DB with some ODBC based BI or Reporting Tool Use a Reporting Database instead Use OpenEdge Replication to create a D/R, Reporting DB Copy on another Server Look @ BravePoint’s Pro2SQL Product Regularly run UPDATE STATISTICS 5 BravePoint 2010 Top Destroyer #2 Developers who don’t understand the Progress Indexing Rules They are reasonably well documented Progress Documentation Progress Performance Tuning Guide 6 BravePoint 2010 Top Destroyer #3 Poorly Tuned Databases Crucial Database Parameters & Helpers: -spin (DB Startup) -blocksize (prostrct create; Unix/Linux) APW/BIW/AIW Processes -B (DB Startup) -bi (proutil truncate bi) 7 BravePoint 2010 Top Destroyer #4 Poorly Configured Databases Database block size (-blocksize) of 4K (AIX/Linux) or 8K (all other IX) Not using Type 2 Storage Areas Tables or Indexes stored in the Schema Area AI Extents not separated from DB/BI Extents (mainly for integrity, not performance) 8 BravePoint 2010 Top Destroyer #5 Not using After Imaging Although that’s more of a Database or job future destroyer than a performance destroyer 9 BravePoint 2010 Top Destroyer #6 Not performing a Regular Dump & Load Using Type 2 Storage Areas does NOT mean you’ll never need to D&L again – don’t trust anyone who told you that Monitor Scatter & Fragmentation in proutil dbanalys reports 10 BravePoint 2010 Top Destroyer #7 Poorly Tuned AppServers & WebSpeed Agents Important Parameters: -mmax # -TB 31 -TM 32 -q -Bt # 11 BravePoint 2010 Top Destroyer #8 RAID 5 RAID 5 on most Disk Arrays and SANs penalizes Write Performance up to 50% (i.e. 2X slower) 12 BravePoint 2010 Top Destroyer #9 Monitor Java (or the processes that use Java) WebSpeed Broker AppServer Broker Admin Server Name Server Tomcat Watch for excessive memory use or high CPU utilization 13 BravePoint 2010 Top Enhancer #1 Shared R-Code Libraries (also known as Memory Mapped Libraries) Conserve Memory because code is shared rather than in each Client’s private memory Code execution is much faster 14 BravePoint 2010 Top Enhancer #2 Stripe (RAID 0) Database Disks Not required for the AI or BI Disks JBOD is sooo 90’s 15 BravePoint 2010 Questions? For further info (not free): [email protected] +1 541 908 3437 (Available 24/7) Alternatively 770-449-9696 X3911 www.BravePoint.com 16 BravePoint 2010