You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Foivos recently realised that padding fields added to classes get dead-code eliminated in native image.
Performance sensitive code often relies in tricks like that to avoid fail sharing. For native image, one could add register those fields for reflection access, but that's a fairly expensive thing to do in terms of build times, native executable size...etc. It would be nice to have a way to register fields such that they don't get dead-code eliminated.
The text was updated successfully, but these errors were encountered:
The thing is: it really matter? false sharing is a problem for high concurrent and high thoughput contended uses cases: sometime is just not worthy and having smaller dataset is better, so...let's think about it where it happens...and I can help to detect the hot spots, see netty/netty#12496 and netty/netty#13945
Foivos recently realised that padding fields added to classes get dead-code eliminated in native image.
Performance sensitive code often relies in tricks like that to avoid fail sharing. For native image, one could add register those fields for reflection access, but that's a fairly expensive thing to do in terms of build times, native executable size...etc. It would be nice to have a way to register fields such that they don't get dead-code eliminated.
The text was updated successfully, but these errors were encountered: