Hello

I am cloning sensors with PrtgAPI. As soon as I start the PowerShell script the memory consumption on the core server is increasing dramatically. Do I make a mistake? Can I free this memory again?

After 10 Sensors the free memory on the core is going down by 5 percent

BR Thomas

Article Comments

Dear Thomas,

in such cases, the first question would be which PRTG version you are using. (There were memory leaks in older versions, which are closed now.)

If you employ the API to interact with PRTG, please make sure to include some delay between the API calls, to give PRTG time to finish the tasks. If you for example add a five-second delay between each call, does the memory consumption still goes up by that much?


Oct, 2018 - Permalink

Hello

We have Version 18.3.43 running. I am using PowerShell with PrtgAPI. The process is: 1) copy the sensor 2) 30sec delay 3) activate the sensor Loop

Shall I close the server connection? Will this release the memory?

Thomas


Oct, 2018 - Permalink

Dear Thomas,

the connection should not consume a relevant amount of memory. We however are analyzing the memory consumption of API calls in general. Some apparent leaks are not leaks, but the memory for object in question is not freed and instead kept for possible later use.

As we are working on the PRTG internals, we also look at the management of the memory. There is no quick solution, as the issue is quite complex.


Oct, 2018 - Permalink

Hello Arne

In the moment the core server has only 16GB RAM. During normal operation about 32% RAM are free. When I start cloning the value is going down to 27 %.

I will try to implement the newest update, mabe this will help a bit

Thomas


Oct, 2018 - Permalink

Dear Thomas,

the aforementioned work on API calls will take time. It could take several releases.

In this case, important questions is if each ten calls cost you another 5 percentage points, or if there is just that initial cost.


Oct, 2018 - Permalink