JNI.....................?

Question

Java

It is necessary to work with files and data archives in java. The speed of execution of this code is very critical. Is there any reason to rewrite work with the file system on native code with java?

Answer 1

Depending on what operations, all libraries that use archiving are already optimized and programmers are happy about this.
I don’t clearly know the specific task, but if we assume that most of its functionality is tied to IO, then rewriting does not make sense, because IO operations are quite slow and most likely blocking, only (as mentioned above) fixing the application logic. But if a compression algorithm or something similar (to Java) is used somewhere, then it makes sense to rewrite it in native, but it seems that there is no such thing in the task.

Answer 2

There is a reason to work out / optimize the architecture of the application well, and it is possible to use JNI only if you stuff large autonomous pieces of critical code into the native part, and not separate operations. And there is no guarantee that this will give a tangible performance boost.