Brand new 2016 print server problems, very high CPU and high network usage

[nikaso]

So we had some ongoing issues with our old print servers and I took the opportunity to consolidate these into one new Server 2016 print server which is also the primary Papercut server. We are still having ongoing high CPU issues however despite it having 4 CPUs assigned in vmware and I've also noticed the network usage is anything from 1 to 2 Gbps throughout the day which seems very high to me.

 

We get very slow printing and issues with client print spoolers stopping randomly (presumably because of not being able to contact the print server). We've tried loads of different things but to no avail, anyone any ideas?

[howartp]

How many users have you got going through Papercut?

 

We had the same issues as you describe, though 2008 R2, but we were still using the builtin DB for 1700 users.

 

Tech Support advised us to migrate the DB to SQL (guides on their website) and it's been hunky dory since.

 

PEter

[nikaso]

How many users have you got going through Papercut?

 

We had the same issues as you describe, though 2008 R2, but we were still using the builtin DB for 1700 users.

 

Tech Support advised us to migrate the DB to SQL (guides on their website) and it's been hunky dory since.

 

PEter

 

We've got about the same number of users but I've just had tech support from Papercut on a remote session and when we stop all the Papercut services it makes virtually no difference to the CPU usage implying it's not a Papercut problem. The only thing I have found so far that makes a big difference to the spooler subsystem app CPU usage (which is the main culprit) is disabling the network adapter. When this is done the CPU usage drops off a cliff.