Difference between revisions of "Thread:Talk:ScalarBot/Version History/Java static keyword bug???"
Jump to navigation
Jump to search
m (New thread: Java static keyword bug???) |
m |
||
| Line 1: | Line 1: | ||
| − | I've been experiencing noticeable performance regression after a refactor, which theoretically with only difference being an static keyword was added to a private final double[] (whose content is never changed). | + | I've been experiencing noticeable performance regression after a refactor, which theoretically with the only difference being an static keyword was added to a private final double[] (whose content is never changed). |
removing that "static" keyword immediately return my performance back, and adding it back effectively decreased my score, so I'm pretty sure that is the reason. so here is my question, how Java handles static final arrays? may that be some bug introduced by optimizations? | removing that "static" keyword immediately return my performance back, and adding it back effectively decreased my score, so I'm pretty sure that is the reason. so here is my question, how Java handles static final arrays? may that be some bug introduced by optimizations? | ||
Revision as of 16:12, 30 November 2017
I've been experiencing noticeable performance regression after a refactor, which theoretically with the only difference being an static keyword was added to a private final double[] (whose content is never changed).
removing that "static" keyword immediately return my performance back, and adding it back effectively decreased my score, so I'm pretty sure that is the reason. so here is my question, how Java handles static final arrays? may that be some bug introduced by optimizations?
