I've installed VSA 18.104.22.168 into HyperV VM with the following spec
I find the SQL to be constantly consuming 25-50% CPU. Is this normal?
Depends on a lot of things - how many agents, how many audits, agent procedures, monitor sets etc. are running, how big your SQL database is, your server respources (cpu cores, disk system etc.).
We run between 300 and 400 agents on 4 cpu cores, 10Gb ram, SAS disks and have a 30Gb SQL database; long term SQL cpu load is <1%.
visit http://<yourvsa>/SystemTab/vsaDisplayStats.aspand review the performance stats to identify where the load is coming from.
usually, you'll find your server is under-spec'd for the workload. ...that's my first guess in your case.
This is a fresh install so there are no agents. I'll try looking at that URL.
I notice after a patch or restart of the system CPU related to SQL is generally high for awhile but then settles back down.
Won't go into server specs but 9.4 does seem to run a little bit higher on load time after a reboot with the same amount resources on it's ESXi host but seems to settle down after a bit. After it seems to run like 9.3.
we have a brand new split build out when we upgraded from 9.3 to 9.4
Currently have 9200 agents
Version Number: 22.214.171.124, Installed Patch Level: 126.96.36.199
KSERVER 24GB RAM, 8 CPU, WINDOWS 2016 STANDARD VMWARE 6.0
KSQL 24GB RAM, 8 CPU, WINDOWS 2016 STANDARD, SQL SERVER 2016 STANDARD, VMWARE 6.0
KSERVER averages about 40% CPU and 40% MEM
KSQL averages about 35-50% CPU and 85% MEM
Since the upgrade and splitting the IIS and SQL server roles, my tech teams (about 50 users) have reported much better performance, less latency, less time switching tabs, etc.
Overall looking good so far. Wish the REFRESH worked, but i hear it is being worked on.
It all depends a lot on the stuff you use, but 24 GB for that VSA on 9200 agents sounds about right.We use 14 GB for 5800 agents. Memory about 80% in use and CPU around 10% (W2K8 R2).
We do use a lot more SQL memory, 32 GB for the same 5800 agents, compared to your 24 GB for 9200.Memory in use normally around 85% and CPU on average between 5 and 10% for SQL2008R2.
We're on the verge of migrating the lot to two new W2K12R2 servers with SQL 2014.We don't trust W2K16 and SQL2016 as of yet.Talking to Kaseya our choices were confirmed as sensible.