Securenode Memory usage.

[GroovyGrovesy]

I initially posted this in the secnodetracker github but was asked to post it here instead.

I have a 2GB Linode with 4GB of swap and I kept getting exceptions so when I checked and zend was using a massive amount of memory (RAM & Swap) whilst it was just sitting there idle.

I restarted zend but when it came back up it was using the same amount of memory. I then stopped both zend and the tracker then started them in the same order and now the memory useage is back to an acceptable level

So when the next challenge was run the Memory usage jumped back up as expected but stayed there long after the challenge finished.

This is my node on the tracking site, both the wallet and tracking software are the latest version (zen: 2001050 tracker: 0.0.8).

I'm waiting for the next challenge to see if it happens again, I'll update here when it does..

[WaveringAna]

It's the sheilded transactions, they take about 3-4gb memory due to how resource intensive they are

[WaveringAna]

Unfortunately there's no way to force an operating system to reduce the allocated heap without being a feature creep

[asbachb]

I think it would be better if the memory would be freed after the challenge ran. So the vps won't need to allocate the entire ram. This might cause less problems with the hosters when they overprovision their hardware.