Viewing profile — dbg_nsk
dbg_nsk
HN member- Joined
- Thu, Sep 28, 2017, 2:36 PM UTC
- HN karma
- 17
- Public activity
- 9 items
- HN profile
- View on Hacker News ↗
About dbg_nsk
Excelsior JET team blog: https://www.excelsiorjet.com/blog My twitter: https://twitter.com/dbg_nsk
Recent public activity
-
comment
Comment #16444122
Right, but even a single instruction placed on every backward branch and at the epilogue of every method causes noticeable impact on the performance. This is especially important i…
-
comment
Comment #16441167
It would be very interesting to run our sample with Timers on this GC. In that paper I found a link to their implementation, but unfortunately it is unavailable.
-
comment
Comment #16440632
Yes, I wrote this article. No, I haven't read those papers before, but after your comment I took a look at one of them.. and it is very interesting! Thanks for mentioning it. But, …
-
comment
Comment #16438285
You are right, such things as value types or inline arrays are not introduced in Java language (yet), but still JVM can allocate objects including arrays on the stack if this objec…
-
comment
Comment #16438102
Yes, an excellent point. Unfortunately, we do not have such specific benchmarks at the moment (only general benchmarks on the performance of GC), but I guess we should add them. Ho…
-
comment
Comment #16437211
Yeah, we've tried that. It was one of the attempts of improving conservative GC (no dead values on the stack => no false roots). Unfortunately, it causes noticeable performance deg…
-
comment
Comment #16437138
Absolutely agree with you about finalizers! However, please note that this "threadReaper" code is from JDK class, so, the problem can appear on every application that just use Time…
-
comment
Comment #16436994
The problem is that it all depends on the liveness of the variables. The same value on the stack can be a root at the begining of the method as the corresponding variable is still …
-
comment
Comment #15357381
hi, feel free to ask me any questions about the post