Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Seperate front- and backend

Michel

August 19, 2015 09:43

I'm using a RDS server for all sysadmin tasks on our network. On of which is PDQ Deploy/Inventory. I'm using it pretty heavily with frequent scanning and schedules resulting in pretty high CPU usage for both services. At times, when various scans and schedules run simultaneously, this results in a pretty high performance impact. Even tho the server has 4vCPU's and 12GB of RAM.

I was wondering is there's a way to seperate the front- and backend of both programs. For example, the services run on a different server than the GUI.

Comments

2 comments

Joel C
August 19, 2015 17:32

Are you running VMware? I assume so due to the "4vCPU" comment.

In VMware adding more resources to a VM does not necessarily mean improvement or performance. In fact, adding more resources can contribute to over-provisioning and cause the server to run slower when trying to grab the additional CPU cycles from the hypervisor.

Here's a good read on this - http://www.zdnet.com/article/virtual-cpus-the-overprovisioning-penalty-of-vcpu-to-pcpu-ratios/

0
Michel
August 20, 2015 06:55

Yes we're running VMWare and you're right, it isn't neccesarily a solution to performance issues. We didn't upgrade from 2 to 4 just because of PDQ, and it helped the overall performance by quite a bit. PDQ just asks a lot of the CPU's the way we use it I guess, that's why I was wondering if I could use a dedicated inventory/deployment service while keeping the front-end on my management server.

0