new version really, really slow
I'm not sure if it's the server or pdq but the latest updates to PDQ have really slowed down PDQ deplOy & inventory. What used to take a few seconds (maybe 5) now is taking 20-30 seconds to process. Like opening pdq takes that long to load. Has anyone else noticed this?
0
Comments
Jonathan,
Are you seeing this performance problem with both Deploy and Inventory or is it mainly in Inventory? We did discover a problem with release 1 of Inventory 2.0 which can cause a slow down in some environments and put out a release 2 a couple days ago to address it. Otherwise if you're seeing a slowdown of both it may be due to .NET. Do a repair of .NET framework 4 and see if that helps.
It was both but mainly deploy is the slowest now. Sometimes I’ll get a “not responding” title on the title bar.
Jonathan,
There may be some issues with your database. How large is your database file? How many deployments do you have listed in All Deployments? We're aware of some possible problems if the number of deployments grows very large which we're working of optimizing. If you don't need the historical data you can try to clean up the old deployments.
It only shows 62 deployments. That can’t be large? Em, where is the database file located so I can see the size?
62 isn't many, that shouldn't be a problem. The database file is located in "%ProgramData%\Admin Arsenal\PDQ Deploy\Database.db".
Have you had a chance to try a .NET 4 repair? It may be a long shot but it's helped out in the past with some strange behavior.
The db is only 344kb so that can't be it.
I haven't done the .net repair since this server hosts other services besides pdq & I don't want to mess them up with repairing .net.
I think the slow issue is a combination of the new version & the upgraded anti-virus on the server. When I disable the anti-virus pdq opens up about 5 seconds faster. Still slow but faster than when anti-virus is on.
You could try the database on another computer (or send it to us to try in our lab) that would narrow it down to something specific to the database or the computer. From there we could narrow it down further.
FYI,
Another thing I've tried to speed things up is also adding my repository location to the real-time scan in Trend Micro. This seems to have sped things up so they don't lock up when I'm browsing my repos from PDQ. Before I added that exception I could literally be waiting 20 seconds for an installer package to show or if I lost patience & tried viewing another installer PDQ would say NOT RESPONDING in title bar. Also the DEPLOY ONCE button now doesn't take another 20 seconds to load the window.
Thanks, that's good feedback. There must be some places where it tries to read the read the repository in the main user interface thread that we need to push to a background. We try to move all file access stuff to the background (especially if they're on shares) but we must have missed some.
I have been having the same kind of issue. A lot of "Not Responding"
System is Windows 7 Pro, 8GB Ram
PDQ Deploy 2.2 release 2 Pro Mode
I do not have Trend Micro.
Database file is 200kb
Doing a .net repair now.
See if it changes anything.
Warren, you don't have to have Trend Micro to have this issue. You just have to have some type of malware protection doing real time scans. If you have such software try disabling & see if PDQ starts up faster. If so, that's part of your slow problem. You have to tell that software to avoid "scanning" PDQ sections.
Spot on, It was MS Security Essentials that was running the Real-time protection. Disabled it and restarted the service and it seems like things are running like they should be.
Thanks
On both server 2016 and windows 10 , i am finding the GUI almost unusable
Click .... Wait ..... Menu fades in slowly then Appears (Both inventory and Deploy)
Server 2016 is super quick for everything else as was my desktop windows 10 machine , moved to server2016 thinking it might be a 10 issue
Deployments and Scans are quick , i only have 20 machines to manage
@Paul Flanders
Is it slow on a fresh install too?
Please sign in to leave a comment.