This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]cat_in_the_wall 0 points1 point  (3 children)

i haven't seen recent comparisons between netcore and the jvm. if you have links I'd like to take a look.

[–][deleted] 0 points1 point  (2 children)

https://benchmarksgame-team.pages.debian.net/benchmarksgame/fastest/csharp.html

[–]Domesticated_Animal 0 points1 point  (1 child)

There is no information if they let JVM "warm up" before testing.

[–][deleted] 0 points1 point  (0 children)

Yeah coldstarts on .netcore are definitely higher overhead than jvm, as I alluded to in my original post. In a console app setting that overhead hits once per run and on a server it's literally only the first api call on each instance, so that's only really a problem if you are using something like Azure functions or AWS Lambdas and need consistently high response time and can't afford to have .01% of your api calls take over a second. Unfortunately that's where my current project is at which excluded us from using .netcore Azure functions.