Try specifying a garbage collector manually. Concurrent Mark Sweep is a good general purpose one that provides a good balance between low-pause and reasonable throughput. If you are on Java 7 or later Java 6, G1 collector is probably better since it is able to also prevent memory fragmentation. You can check the Java SE … Read more
The original scientific article (“Garbage-First Garbage Collection” by Detlefs, Flood, Heller and Printezis) contains some details on actual measures (in section 4).
I think you will find many suggesting this style of pattern. Not just me or Henk DBContext handling Yes, Ideally Using statements for DBContext subtypes Even better Unit Of Work patterns that are managed with Using, that have a context and dispose the context Just 1 of many UoW examples, this one from Tom Dykstra … Read more
Dispose is for releasing “unmanaged” resources (for example, sockets, file handles, Bitmap handles, etc), and if it’s being called outside a finalizer (that’s what the disposing flag signifies, BTW), for disposing other IDisposable objects it holds that are no longer useful. “Unmanaged” resources aren’t managed by the CLR (hence the name), and GC doesn’t mess … Read more
This answer to this question is as found here: Python PySide (Internal c++ Object Already Deleted) Apparently, assigning one widget to QMainWindow using setCentralWidget and then assigning another widget with setCentralWidget will cause the underlying c++ QWidget to be deleted, even though I have an object that maintains reference to it. Note: QMainWindow takes ownership … Read more
It looks like PyTorch’s caching allocator reserves some fixed amount of memory even if there are no tensors, and this allocation is triggered by the first CUDA memory access (torch.cuda.empty_cache() deletes unused tensor from the cache, but the cache itself still uses some memory). Even with a tiny 1-element tensor, after del and torch.cuda.empty_cache(), GPUtil.showUtilization(all=True) … Read more
As of JDK 18, no. JDK 18 omits enclosing instance fields from inner classes that don’t use it. However, prior to JDK 18, yes, instances of anonymous inner classes hold on to a reference to their enclosing instances even if these references are never actually used. For example, this code: public class Outer { public … Read more
CPU have different level caches L1, L2, L3. Every CPU (and also /may CPU Core) has own cache. This caches store minimal set of main memory (RAM) for performance. _______________ ______________ | CPU 1 | | CPU 2 | | _________ | | _________ | | | Level 1 | | | | Level 1 … Read more
Remember what Azul used to do: make customized multicore Java appliances. An Azul machine might have 60 or 100 cores and there was all sorts of cleverness to take advantage of the parallelization (the one that impressed me was the optimistic locking: a thread that was supposed to obtain a lock just assumed that it … Read more