Java vs C app performance – Gary explains

21 thoughts on “Java vs C app performance – Gary explains”

1. I heard some modern ARM processors can run Java bytecode natively… I wonder how much that changes the performance.

2. Maybe interesting to compare this again(4 years later, using GraalVM on a desktop). What I think should have been compared also, is actual runtime. So no compiler delay included. Cheers

3. i wonder why all unix and linux and windows operating systems as well as several major databases don’t just switch over to java if it’s faster and drop c and c++

4. Ok… I am not convinced at all

5. We are in 2020 and we still compare C to some other garbage languages in term of performance!! I mean really!! This doesn't need comparaison even lol

6. May be this the reason still C is better. C is doing their work for him host one time in life. But Java doing Everytime. They called this is platform independent, let's enjoy it who cares about nano second when built a big webapp. But these sha things scary in Java webapp

7. First impression, Java byte code are not zeors and one.

8. c: #include <stdbool.h> 😉 std type headers make life a bit easier (if you can use -std=c99)

9. One thing worth to mention about Java programs is the advantage of the bitecode to use features of future architecture through the JVM, while in C/C++, you need to recompile to machine code in order to utilize the same features. So, unless you recompile your C/C++ software, that initial performance gap between Java and C/C++ will disappear or move in favor of Java if you swap CPU. That's actually a great feature many applications, like servers that need to swap hardware but still need to provide services 24/7 or even at home if you built your new PC and you just swapped the OS drive. So, if anything, with Java you can be sure that every time you run your program, the software will use all the features of your CPU to the fullest extent.

10. What about unreal?

11. Nice

12. java is trash i hope one day that Grabage collection that it uses, Removes java alltogether.

13. Even .net platform is much faster then java platform

14. C could probably beat Java even in that case using march

15. commento portafortuna

16. I am watching a low information "expert." The very first thing he talks about is only superficially accurate, and at best misleading. He talks about the JVM, and misinforms the viewer on the topic, insinuating the java byte code is interpreted at runtime when it isn't, it is compiled at runtime. Leading with misinformation is an interesting choice, leading to the conclusion that this "expert" here isnt one and doesnt even know that he is being misinformative. This quack is regurgitating information produced by someone else, and he didnt even bother to question the veracity of any of it. He didnt run any "tests" .. certainly not reasonably valid ones.

17. you should compare c++ cus that is more close to the cpu

18. This is just arithmetic, the simplest of simplest to implement computing feature. Try adding tests where you have to allocate and deallocate gigabytes of data (like any app with a dynamic GUI would). Also try doing something with strings, or move to a Java vs C++ comparison, and bench some OO paradigms (like just about any app would). Java will be at least 100x slower.

19. slightly? you're kidding right?

20. Every person that dont know how to code, would look at these results and pick C…so why thats not the case with programmers? Lazyness?

21. The butt-hurt C guys in the comments…haha. Love it.

Comments are closed.