Re:Atlassian's new terms forbid benchmarking
by ex_atlassian on Saturday September 29, 2018 @11:23PM
(#18104293)
The hyper distributed micro services are definitely one of the big reasons for unnecessary complexity and latency problems. It was surprising for me to see that the JVM based services were load tested for 4-10 minutes to call the test successful.
[ Parent
| on HN ]
Re:Atlassian's new terms forbid benchmarking
by beepbeepbeep1 on Sunday September 30, 2018 @03:46AM
(#18105076)
Yeah it's odd as some very clever talented people have passed through there doors, some very mixed feelings towards them.
The JVM is just getting warmed up load testing for that short a period.
Re:Atlassian's new terms forbid benchmarking
by therealdrag0 on Monday October 01, 2018 @08:00PM
(#18117801)
Do you know of any sources that show it takes that long to warm up JVM?
Re:Atlassian's new terms forbid benchmarking
by bitcharmer on Tuesday October 02, 2018 @02:42AM
(#18119293)
It has nothing to do with time and everything to do with the number of times hot paths get executed.
On a server JVM instance a method will have to be executed (by default) 10 thousand times before it is compiled.
There is also a question of how stable the compilation profile is and how likely deoptimizations are but that's a different story.