On Wed, 5 Apr 2023 08:19:50 GMT, Maxim Kartashev <mkartas...@openjdk.org> wrote:
> Getting bounds of a `GraphicsDevice` and insets of a screen are fairly > frequent operations. When working over the network (remote X session), those > can take several *seconds* to complete, introducing repeated freezes even > when typing in an editor feels only slightly sluggish. > > On the other hand, neither bounds nor insets change very often - if at all - > during the lifetime of an application. So caching their values seems like a > natural solution to the problem. The caches need to be reset only when > there's a possibility of change in the screens configuration. > > A similar patch has been living in [JetBrains > Runtime](https://github.com/JetBrains/JetBrainsRuntime/) for well over a year. What exact operation is slow? ------------- PR Comment: https://git.openjdk.org/jdk/pull/13346#issuecomment-1497161488
