On Wed, 19 Feb 2025 15:27:25 GMT, Matthias Baesken <mbaes...@openjdk.org> wrote:
> So what's the opinion, should we go for SIZE optimization for libjdwp? > My idea was that the current setting LOW indicates that the lib is not super > performance critical; so SIZE might be a nice option ? I'm not sure how the decision was made to go with LOW for libjdwp. Much of what it does is transactional over the wire, so probably not subject much to code performance, but there are some more heavyweight tasks that the debug agent needs to do, especially when dealing with a a large number of threads. I'd like to see those tasks sped up if anything. It seems LTO would be good to enable regardless of the optimization level. One thing you haven't given numbers for is LTO+HIGH. Based on the other results so far, seems the footprint would be slightly below to the current LOW setting (maybe 3-4k). When faced with a decision like this that doesn't have concrete data as to what the right choice is, I'd tend to go with the status quo and make no change, although it seems going with LTO should be a good choice no matter the opt level unless there is some other possible negative side affect of doing so that hasn't been brought up. ------------- PR Comment: https://git.openjdk.org/jdk/pull/23563#issuecomment-2669266484
