Hi Veemzatetujecpu2121!
Yes, we've included several fixes for the existing sql queries in v5. If you still see high cpu consumption with v5 please raise a support case and share the case ID with us. Cheers!
-
- Product Manager
- Posts: 14396
- Liked: 1568 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
-
- Novice
- Posts: 9
- Liked: 2 times
- Joined: Apr 17, 2015 11:21 am
- Full Name: Danny Heijl
- Contact:
Re: SQL server cpu usage on idle state
What I noticed: after installing Agent for Windows V5 I still had higher "idle" CPU usage for SQL Server than what one would expect.
Now after I decided to let Veeam recreate the database (for an unrelated issue) SQl Server CPU usage seems to have dropped dramatically...
I'd been running Veeam Agent for Windows for years on this machine, upgrading Veeam Agent as required without ever recreating the database.
Now after I decided to let Veeam recreate the database (for an unrelated issue) SQl Server CPU usage seems to have dropped dramatically...
I'd been running Veeam Agent for Windows for years on this machine, upgrading Veeam Agent as required without ever recreating the database.
-
- Enthusiast
- Posts: 50
- Liked: 9 times
- Joined: Feb 13, 2014 10:11 am
- Contact:
Re: SQL server cpu usage on idle state
Just to update on this. Since this for years have been killing battery on all the labtops I have been involved with, I have taken to disabling Veeam Agent on my machines until I need it for a manual backup.
There is at least 10 -15% longer batterylife on my laptops when the Veeam Agent is disabled as a service.
It's a huge CPU consumer combined/based off of the SQL service when its just supposed to be idle.
There is at least 10 -15% longer batterylife on my laptops when the Veeam Agent is disabled as a service.
It's a huge CPU consumer combined/based off of the SQL service when its just supposed to be idle.
-
- Product Manager
- Posts: 14396
- Liked: 1568 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: SQL server cpu usage on idle state
Hello folks,
New Veeam Agent for Widows v6 runs on SQLite engine and no longer requires localdb, specifically to address this problem. Please upgrade to v6, remove the localdb (unfortunately it has to be removed manually after upgrade, but please make sure that no other apps are using these SQL components) and let us know how new version behaves in your environment. Thank you!
New Veeam Agent for Widows v6 runs on SQLite engine and no longer requires localdb, specifically to address this problem. Please upgrade to v6, remove the localdb (unfortunately it has to be removed manually after upgrade, but please make sure that no other apps are using these SQL components) and let us know how new version behaves in your environment. Thank you!
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Mar 05, 2023 11:47 pm
- Contact:
Re: SQL server cpu usage on idle state
Hey,
i was searching for this issue earlier and was delighted when i stumbled about this thread, seeing that a (maybe) solution was very recently released.
The good thing:
- getting rid of the SQL localdb vastly reduced the memory usage when idle for me, down from about 500mb for the sql process to about 50mb for the Veeam service for me
- backing up my box still works fine
But now the Veeam service (Veeam.EndPoint.Service.exe) itself is using quite a lot of CPU time when it should just be doing nothing while waiting for the next job.
Still not correct behaviour imho.
i was searching for this issue earlier and was delighted when i stumbled about this thread, seeing that a (maybe) solution was very recently released.
The good thing:
- getting rid of the SQL localdb vastly reduced the memory usage when idle for me, down from about 500mb for the sql process to about 50mb for the Veeam service for me
- backing up my box still works fine
But now the Veeam service (Veeam.EndPoint.Service.exe) itself is using quite a lot of CPU time when it should just be doing nothing while waiting for the next job.
Still not correct behaviour imho.
Who is online
Users browsing this forum: bct44, Bing [Bot] and 33 guests