Ours is very similar to yours, within 10% in most cases.

What if your server configuration?  Are these physical or virtual servers?

They are virtual machines. could you post yours PLEASE .. you can just copy and paste the stats here.

We're running a much smaller system:

Agents Currently Online: 803
Total Licenses Used: 1,118
Kaseya Version: 6.2.0.0

The VSA and the SQL are on separate servers, with the VSA being a virtual machine.  Both were IPL'd on the 11th.

That was VERY interesting

2 points of interest

1 our connections keep going up until a restart

2 you also saw a massive increase in Locks at the same time as us. For us this brought the server to a stand still and we had to reboot. So it must have been a Kaseya update or something.

Any one else want to share there performance  

;) we tracking the lock issue very closely before we upgraded to K2, but honestly I haven't looked those numbers in over a year.  Back then the Kaseya maintenance process involved blasting and rebuilding the database schema every night.  The ksubscribers database also accounted for more active connections to the database than nearly all of our other systems combined (Kaseya is one of about 20 systems that use that database server).  I believe they've gotten a bit smarter with their nightly maintenance, but not much.  Database connections continue to be a problem.

I obviously left out a couple of the tables (the Current Tasks waiting for CPU and Database IO Distribution tables were too long) but one thing I should have mentioned is that we're not using Kaseya's internal database backup system.

Dose anyone else want to join the fun and post their stats please

Also this info can't be right ?

SQL Server Configurations

Physical Memory (Bytes) 549,745,152,000

AWE Memory (Bytes) 260,810

CPU Count 64

Hyperthreaded Ratio 16

Buffer Cache Hit Ratio (should be > 95) 99.87%

Yes, those are accurate numbers.  It's a Dell PowerEdge R910 with 8 quad-core CPUs.  We like to joke that it only has 1/2TB of RAM because our boss is cheap and didn't want to go for a full TB.

You are Dead to me

Right so can some one  with realistic hardware post now ! lol

oh and can i come work with you Bill

Michael Dixon

You are Dead to me

Right so can some one  with realistic hardware post now ! lol

oh and can i come work with you Bill

This probably isn't the year to join the cotton industry.  Cotton production in TX is projected to be just 3M bales due to the drought, compared to 8M bales last year.  Sadly, that server is going to loaf this year... but there's always next year!

But everyone is missing the big question.  If you implement a Kaseya server with such staggeringly good hardware, is Kaseya still slow as heck to use at the browser????  or is it awesome?

jdvuyk can you post your stats please. You can simply copy and paste that page into the forum when using the rich formatting option.

I am literally in the middle of moving to a new server environment today/tomorrow.  So not a lot of point.  But I have found over the last couple of years that:

1) It doesn't seem to matter how good your hardware is, in some situations the Kaseya is just slow at the browser.  This has been well documented by many.

2) When I get periods of slowness the server appears to be doing very little.

Im not too worried about going into an in-depth, I'm just curious.  Does a awesome server = awesome experience.  

he probably would know what we suffer so couldn't comment

Interesting stats guys.  I'd add mine but there's little point at the moment as most of our clients are still on one our 5.1 servers.  We have a 6.1 server but it's only got a few hundred agents on it at the moment.  Our biggest 5.1 has just shy of 11k agents on it and on a busy auditing day it slows down.

What we did do was throw as many disks at the SAN as we possibly could and this improved things quite dramatically.

Once we've got a few more sites installed I'll post our stats here too.