That may cause significant performance issues. Storage HEAP memory exceeding 10GB may cause performance problems when the garbage collector works. Reading takes a lot of time, data is copied through various buffers, and we use memory, threads and external resources massively. Storing large videos on external resources is inefficient.

The movie database can contain several hundred items of various sizes, from 0.5 to 2GB each. Write a platform that enables efficient video streaming for many online users. That’s why today I would like to show you how to reconcile fire and water and deal with a vast storage need while still having a small, high-performance application in Java. This is shown in movie files, which previously couldn’t reach even 1GB and now have increased to over 2GB for 4K resolution. Meanwhile, operational and mass memory has become cheaper for several years and is no longer such a problem as before. Larger amounts may cause performance drops, and with a size above 10GB, serious problems can be expected. Indeed, everything depends on various factors, but it’s assumed that a single application instance should not occupy more than 2GB of memory bytes.

As a result, a programmer doesn’t even have to be familiar with the mechanisms of operational memory usage.Īlthough the GC algorithms are constantly improving, they are still based on the frequent copying and optimizing of memory blocks. The well-known Garbage Collector mechanism is responsible for all of it. We all know that Java JVM automatically allocates and cleans the application memory.

Java to kotlin online converter