- Posts: 2
- Liked: never
- Joined: Oct 26, 2020 11:24 am
- Full Name: Samuel Hibbert
We have noticed that the Veeam.archiver.proxy used an insane amount of CPU & RAM on our repo servers. We have found a few posts talking about changing the number of threads.
We are looking for what people might recommend on the number of threads the proxy can use? the default looks to be 64. Is there a Veeam recommendation or is it just play with the settings until you find the right fit?
- Veeam Software
- Posts: 1726
- Liked: 349 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
When active, a proxy consumes CPU and RAM a lot (and that's expected). By reducing the number of threads you will lower the load on resources, but at the same time, it'll result in slower backups. There's no recommendation other than using the defaults, and when adjusting threads it's indeed a hit-or-miss play.
Another thing to note is that some RAM is also consumed by the Jet engine. You can check for more details in our Best Practices guide.
Users browsing this forum: No registered users and 4 guests