1 / 49

Hardware Recommendations to make installations hum

Hardware Recommendations to make installations hum. Eric Wauters i Facto Business Solutions NV Development Manager. April 17, 2008. Agenda. Basics Native DB Server SQL Server Terminal Services Clients & NAS Network. Agenda. Basics Why pay attention to hardware?

wauna
Download Presentation

Hardware Recommendations to make installations hum

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hardware Recommendations to make installations hum Eric Wauters iFacto Business Solutions NV Development Manager April 17, 2008

  2. Agenda • Basics • Native DB Server • SQL Server • Terminal Services • Clients & NAS • Network

  3. Agenda • Basics • Why pay attention to hardware? • Native vs. SQL Server • Core Components • Native DB Server • SQL Server • Terminal Services • Clients & NAS (Navision Appl Server) • Network

  4. Basics - Why paying attention to hardware? • Performance Tuning Areas: • Application: 80-90% • Infrastructure: 10-20% • You need a solid base • Quick fix

  5. Basics - Differences Native – SQL Server

  6. Basics - Differences Native – SQL Server Different server options need different hardware

  7. Basics - Similarities Native – SQL Server • Index is an index, Lock is a lock, Block is a block, Deadlock is a deadlock • Get data fast, Write data fast!

  8. Basics - Core Components Core Components

  9. Basics - Core Components • Memory (RAM) • Processors (CPU) • Disk Subsystem (RAID) • Network • Server settings

  10. Basics - Core Components - Storage Types • RAID 0 • RAID 1 • RAID 10 • RAID 5

  11. Storage Types - RAID0 Logical Layout RAID0 Physical Layout 0 0 1 1 2 3 2 4 5 3 6 7 4 8 9 5 6 7 8 9

  12. Storage Types - RAID1 Logical Layout RAID1 Physical Layout 0 0 0’ 1 1 1’ 2 2 2’ 3 3 3’ 4 4 4’ 5 5 5’ 6 6 6’ 7 7 7’ 8 8 8’ 9 9 9’

  13. Storage Types - RAID1 Logical Layout RAID10 Physical Layout 0 0 5 1 6 1 2 7 2 3 8 3 4 9 4 5 0’ 5’ 6 6’ 1’ 7 7’ 2’ 8 8’ 3’ 9 9’ 4’

  14. Storage Types - RAID5 Logical Layout RAID5 Physical Layout 0 0-1parity 0 1 1 3 2 2-3 parity 2 5 4-5 parity 4 3 6-7 parity 6 7 4 9 8 8-9 parity 5 6 7 8 9

  15. Agenda • Basics • Native DB Server • Hardware recommendations • Server Settings • SQL Server • Terminal Services • Clients & NAS (Navision Appl Server) • Network

  16. Native – Hardware Recommendations • Limited possibilities due to limited support. • 1Gb RAM • 1CPU core • Single database per server

  17. Native - Hardware Recommendations • Dedicated Server • CPU • 1 CPU for NAV (If necessary: second CPU for +40 users) • RAM • 1,5 Gb (1 for NAV; 0,5 for OS) • DISKS • OS – dedicated RAID 1 • fdbfile – dedicated RAID 1 • .fdb > 5Gb •  Split over multiple RAID 1 •  RAID 10 • 15K RPM

  18. Native - Server Settings A few tips: • All database files: same file size • Dedicated fysical disks per file • Use commitcache • Make sure you use a UPS • If creating extra database file: • Backup/delete db/create db/restore! • DB Cache

  19. Agenda • Basics • Native DB Server • SQL Server • Hardware recommendations • Server Settings • Terminal Services • Clients & NAS (Navision Appl Server) • Network

  20. SQL Server – Recommendations - Core Components • Memory (RAM) • Processors (CPU) • Disk Subsystem • Server Settings

  21. SQL Server – Recommendations - Memory Importance memory < > disks = ns compared to ms! CACHE!

  22. SQL Server – Recommendations - Memory 32 bit vs 64 bit • 32 bit directly addresses up to 4Gb of memory (232 = 4.294.967.296 bytes = 4Gb) • 64 bit can address an “indefinite” amount of RAM (264 = 18.446.744.073.709.551.616 bytes = 18.446.744.073,7 Gb)

  23. SQL Server – Recommendations - Memory 32 bit – how to use more RAM? Boot.ini: • /3GB: • Default windows install: • 2 Gb reserved for kernel (OS) • 2 Gb for usermode • With /3Gb: • 1 Gb reserved for kernel (OS) • 3 Gb for usermode • /PAE • “Physical Address Extensions” • memory address extension that enables support of greater than 4 GB of physical memory

  24. SQL Server – Recommendations - Memory 32 bit – how to use more RAM? SQL Server: • AWE: to acces memory over 4Gb • “Address Windowing Extensions” • Address Memory over 4Gb as nonpaged memory • dynamically map views of the nonpaged memory to the 32-bit address space • You must specify /PAE in boot.ini

  25. SQL Server – Recommendations - Memory 32 bit – Server settings • Min/Max SQL Server Memory Set the same for ‘constant’ behaviour • Memory • Check the Windows Server and SQL Server editions limitations

  26. SQL Server – Recommendations - Memory • 32 bit - Warning when using AWE: • Imposes overhead • Adds initialization time • Memory above 4Gb is only for data caching, not for: • Plan caching • Sort space • Lock memory

  27. SQL Server – Recommendations - Memory • What about x64? • Support for large RAM - no boot.ini changes • Not only data caching, also: • Plan caching • Sort space • Lock memory => “Always Rowlock”

  28. SQL Server – Recommendations - Memory • Windows - Maximum Memory • Windows 2003 (32bit) • Windows 2003 Standard = 4GB • Windows 2003 Enterprise = 64GB • Windows 2003 Datacenter = 128GB • Windows 2003 (64bit) • Windows 2003 Standard = 64GB • Windows 2003 Enterprise = 1TB • Windows 2008 (32bit) • Web Edition: 4GB • Standard Edition: 4GB • Enterprise Edition: 64GB • Datacenter: 64GB • Windows 2008 (64bit) • Web Edition: 32GB • Standard Edition: 32GB • Enterprise Edition: 2TB • Datacenter: 2TB

  29. SQL Server – Recommendations -Memory • SQL Server Maximum Memory • SQL 2000 • Desktop Engine = 2GB • Standard Edition = 2GB • Enterprise Edition = 64GB • SQL2005 • Express Edition = 1GB • Workgroup Edition = 3GB • Standard Edition = Operating System maximum • Enterprise Edition = Operating System maximum

  30. SQL Server – Recommendations - Memory IMPORTANT On x64 SQL Server platforms you must give the SQL Service account the “Lock Pages in Memory” privilege in order for SQL to use the available RAM KB Article 918483

  31. SQL Server – Recommendations - Memory • CONCLUSION • Memory Recommendations • As big as you can afford • Rough guidelines

  32. SQL Server – Recommendations - CPU CPU recommendations • Typically NOT a bottleneck • Cores vs Sockets • Disable Hyper Threading • Redundant

  33. SQL Server – Recommendations - CPU • Windows - Maximum CPU Sockets • Windows 2003 (32bit) • Windows 2003 Standard = 4CPU • Windows 2003 Enterprise = 8CPU • Windows 2003 Datacenter = 64CPU • Windows 2003 (64bit) • Windows 2003 Standard = 4CPU • Windows 2003 Enterprise = 8CPU • Windows 2003 Datacenter = 64CPU • Windows 2008 (32bit) • Web Edition = 4CPU • Standard Edition = 4CPU • Enterprise Edition = 8CPU • Datacenter = 32CPU • Windows 2008 (64bit) • Web Edition = 4CPU • Standard Edition = 4CPU • Enterprise Edition = 8CPU • Datacenter = 32CPU

  34. SQL Server – Recommendations - CPU • SQL Server Maximum CPU Sockets • SQL 2000 • Desktop Engine = 2CPU • Standard Edition = 4CPU • Enterprise Edition = 32CPU • SQL2005 • Express Edition = 1CPU • Workgroup Edition = 2CPU • Standard Edition = 4CPU • Enterprise Edition = Operating System maximum

  35. SQL Server - RAID Recommendations • Three Spindles is a must! • WinOS,Page File,SQL Program files,etc. • Pagefile.sys • Transaction LOG • 100% write • Writes all the time (“write ahead”) • Database File(s) • Read: 80-90%, Write 10-20% • Writes at checkpoints

  36. SQL Server - RAID Recommendations • What about TempDB: • Used for large operations (e.g. Reindex), mainly out of hours. • In SQL2005: often 5-10% of IOs on TempDB files.

  37. SQL Server - RAID Recommendations • OS, SQL Program files, etc = RAID1 • LOG File = RAID1 • DB Files = RAID10 • (TempDB = RAID1) • Small disks, not for capacity but for IOPS ! • Do NOT use RAID5.

  38. SQL Server - Disks Summary • Biggest bottleneck • Think “Spindles” not “Capacity” • As fast as possible • 15kRPM • RAID 1/RAID10

  39. SQL Server – Server Settings • MDOP • Auto Create Stats • Auto Update Stats • Auto Shrink – Auto Grow

  40. Agenda • Basics • Native DB Server • SQL Server • Terminal Services • Clients & NAS (Navision Appl Server) • Network

  41. Terminal Services • Memory • 64 MB per Dynamics NAV user + 1 GB for OS • Example: (100 x 64) + 1000 = 7.4 GB or 8 GB • CPU • 10 -15 users per CPU core • Based on client activity; Manufacturing and so on • Disk • 1Gb per user • Based on activity • Network • 1 Gigabit Ethernet

  42. Agenda • Basics • Native DB Server • SQL Server • Terminal Services • Client & Navision Application Server (NAS) • Network

  43. Clients and NAS • RAM • 256 MB or greater • CPU • 2.0 GHz or greater • Disk • IDE (1 GB of drive space) • Network • 100 Megabit (No hubs)

  44. Agenda • Basics • Native DB Server • SQL Server • Terminal Services • Client & Navision Application Server (NAS) • Network

  45. Network • 1 Gigabit Backbone • SQL • Terminal Services • BizTalk • IIS • Application Servers • 100 Megabit • Clients • No hubs only switches

  46. Agenda • Basics • Native DB Server • SQL Server • Terminal Services • Client & Navision Application Server (NAS) • Network

  47. What about NAV 2009? • New architecture  Middle Tier • Only SQL Server

  48. Resources • Microsoft • Partnersource http://www.microsoft.com/dynamics/partnersource.mspx • Windows & SQL Server editions: http://www.microsoft.com/ • Storagesearch.com http://www.storagesearch.com/xtore-art1.html • SQLPerform Ltd. http://www.sqlperform.com

  49. Q&A Thank you for your attention Eric Wauters eric.wauters@ifacto.be www.waldo.be

More Related