Do you think you have maximized your Kaseya Server for your current environment? Are you running into performance issues that are difficult to address? Are you planning for future grown? Well this session is what you were looking for! Join us in this technical session as you hear from Kaseya Experts and how they have tuned Kaseya to scale and manage thousands of devices on a single virtual machine including IIS, SQL and Kaseya specific optimization techniques.
9. Recommended Configuration
● Kaseya Can Scale to three servers:
● Resources for 1k agents
● .5 GHz App Server
● 1 GHz on DB Server
● Typical IOPS
● 15 Application Server
● 40 Database Server
10. Recommended Configuration
● Reporting Services can run on another server
● Typically, memory usage of reporting services is based on
50% of memory upon startup
● You can manually change the ReportServer.conf if
necessary to reduce
● C:Program FilesMicrosoft SQL ServerMSRS10_50.
SYSPREPReporting ServicesReportServer.conf
● <MemoryThreshold>90</MemoryThreshold>
● <WorkingSetMaximum>2000000</WorkingSetMaximum>
● <WorkingSetMinimum>500000</WorkingSetMinimum>
● <RecycleTime>720</RecycleTime>
13. Database Best Practices
● AV Exclusions
● OS defrag & mdf/ldf locks
● Do not enable auto shrink on the
Ksubscribers database
● Above 8 cores, it's best to set parallel
query degree to 4
15. Database Best Practices
● Synchronous replication will cause
performance issues
● Always-On in SQL Server 2012 and
Replication can cause re-apply schema
to fail
16. Database Optimization
● Cache Hit Ratio > 98%
● DiskIO , keep it below 20ms
● TempDB, Broker Services and 6.3
● Seperate Networks
● Maintain it!!
● Rebuild/Reorganize Indexes
● Update Statistics
18. Database Optimization
Typical Memory Usage of SQL Server
● Agents measured by cache/hit ratio
● Calculation is 2Gb/1000 Agents
● Reserve 4Gb Min for the OS
● Log retention and audit details = database
size
19. Database Optimization
● Optimal File Layout can help your
database Performance
● Kaseya Databases are typically 75%
Read and 25 % Writes
● Add multiple data files for Tempdb
22. Kaseya Application Server
● Kaseya recommended configuration is
a Guideline
● Kaseya and SQL on the same server?
How big can it get?
● workloads affect server performance
23. Kaseya Application Server
● Baseline Audits are “expensive”
● Baseline Audits only need to be run once
(Automatically run once when you add the
agents)
● Rescheduling when “out of sync” condition
● Latest Audits are “cheap”
● Can be run daily spread out over 12 hours
24. Kaseya Application Server
● Scripts do take resources, so be careful
how many you run
● Global Policy changes can generate
very large loads on the server
● Monitor counter scans can cause high
CPU spikes (6.2)
25. Kaseya Application Server
● Handling more load with threads
● Kserver Threads
● Messagesys Threads (6.2)
● PluginHost Service (6.3)
26. Hyper Scaling Kaseya
● Split server configuration
● Leveraging multiple SQL Server
Instances
● SQL Server Distributed Views
● For high volume installs
● aggregation apps
● for system of record
● Leveraging Solid State Technologies
31. Networking
Understand latency to endpoints
Leverage CDN's
OOB!!!!!!!!!!
● Most firewalls strip
Firewall Session Management
● 5510x @250k
32. Virtualization
● Set reserves
● Do not restrict, let it fly
● Don't oversubscribe
● Don't allow ballooning
● Backups / snapshots / revert
● Independant mode
● Use tiered storage
● Reduncancy?
33. Leveraging Cloud Providers
● Use VMware monitor counters if
possible to keep host honest
● Beware of adjacency issues
● Kaseya can be spikes
● Test, monitor and understand iops
● Port exhaustion
● Vett network
● Understand SLA's