RFR: 8337217: Port VirtualMemoryTracker to use VMATree

Afshin Zafari azafari at openjdk.org
Fri Nov 8 10:51:46 UTC 2024


On Fri, 27 Sep 2024 11:43:19 GMT, Johan Sjölen <jsjolen at openjdk.org> wrote:

> Why should the default be disabled? That requires customers to explicitly pick the new tree to be used, which they are very unlikely to do. As I understand it, and correct me if I am wrong, the main goal of having two implementations is the ability to revert back in case we have bugs in the new one. If the default is to have the new implementation be disabled, then how are we ever going to find any real use bugs?

You are right. This should be defualt = enabled. Anyway, we are not going to have two versions.

> I don't believe that we have decided that already. Both me and, I believe, Gerard have been negative towards the proposal to keep both implementations. I'd like to use this as an opportunity to discuss the pros and cons of different approaches, which is why I asked for your opinion on my alternative. I believe that it is very important that we all agree on the approach taken, as we will all have to deal with the consequences of that approach.

Sorry for misunderstanding. We go for 1 version only.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/20425#issuecomment-2379619838
PR Comment: https://git.openjdk.org/jdk/pull/20425#issuecomment-2379622866


More information about the core-libs-dev mailing list