FlorianBruckner commented on issue #5555: URL: https://github.com/apache/netbeans/issues/5555#issuecomment-1445273593
This may actually not be a Netbeans issue, but a Swing one. I have been using this piece of sample code here: https://docs.oracle.com/javase/tutorial/uiswing/examples/components/ProgressBarDemoProject/src/components/ProgressBarDemo.java This is as basic as it will get and I really cannot believe what I am seeing here. The progress bar is created with a range from 0 to 100: progressBar = new JProgressBar(0, 100); It starts eating GPU as soon as the value is not 0 or 100. The power drawn from the CPU according to the tool I am using depends on the size of the JFrame. When the JFrame is just tiny, my GPU consumption delta is about 3 watts from baseline. when the JFrame is maximized, the delta is up to 17 watts. While looking at power consumption, the task to update progress was not running, so the application was basically idle. I have been running this on latest Java 8 (i know, ancient), but as this correlates to Netbeans GPU power consumption across 8, 11 and 17 I guess this may be unrelated to the Java version being used. As I said, I am very confused by this result and would ask someone to verify these findings. It may very well be something specifc for my machine or the way I am doing measurements. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
