The short answer To find out how large an object is, I would use a profiler. In YourKit, for example, you can search for the object and then get it to calculate its deep size. This will give a you a fair idea of how much memory would be used if the object were stand … Read more
I don’t see GC.RegisterForFullGCNotification(int,int) anywhere in your code. It looks like you’re using the WaitForFullGC[xxx] methods, but are never registering for the notification. That’s probably why you’re getting the NotApplicable status. However, I’m doubting that GC is your problem, while possible, I suppose it would be good to know about all of the GC modes … Read more
The advantage of recycling an ArrayList (e.g. by calling clear) is that you avoid the overhead of allocating a new one, and the cost of growing it … if you didn’t provide a good initialCapacity hint. The disadvantages of recycling an ArrayList include the following: The clear() method has to assign null to each (used) … Read more
Javascript doesn’t have explicit memory management, it’s the browser which decides when to clean it up. Sometimes it may happen that you experience un-smooth rendering of JavaScript due to a garbage collection pause. There are many techniques that you can apply to overcome glitches caused by garbage collection (GC). More you apply more you explore. … Read more
The fastest I come up with is if you create a new object: var key, keys = Object.keys(obj); var n = keys.length; var newobj={} while (n–) { key = keys[n]; newobj[key.toLowerCase()] = obj[key]; } I’m not familiar enough with the current inner working of v8 to give you a definitive answer. A few years ago … Read more
Note: I have deleted my previous answer and have studied the sources (also build my own JVM just to find out this particular moment), here is the answer. The short answer JVM 11 version (at the moment), will not go below Xms when making the heap smaller. The long answer The absolute truth is in … Read more
There are a lot of things going on here. Let’s take each at a time. It seems you are using a single container per pod (though you could have many containers per pod). The requests.memory and limits.memory are specific to the container, Kubernetes computes limits and requests per pod as the sum of all the … Read more
I know that this question is ancient, but hell – I found it, and I figure that others might as well. I’m trying to resolve a related issue, and might have some insight. You mentioned Dustin Campbell’s WeakEventHandler – it indeed cannot work with anonymous methods by design. I was trying to fiddle something together … Read more
The object will not become a candidate for garbage collection until all references to it are discarded. Java objects are assigned by reference so when you had classObject = myObject; You assigned another reference to the same object on the heap. So this line myObject = null; Only gets rid of one reference. To make … Read more
I can see that several people have gone extreme about not recommending to call GC.Collect. GC.Collect is there for a reason, here are my recommendation of when and why to call GC.Collect. In General, don’t worry about calling it, GC tunes itself very well and will do the right thing. Sometimes, you end up in … Read more