1

I have question how to create a performant swing component.

The component should draw some kind of bar chart. The data for the component are stored in a separte FIFO buffer class. Everytime the buffer is updated the component is informed.

At the moment the component draws a BufferedImage everytime the data changes. The paintComponent method of the bar chart component then draws the created BufferedImage.

Due to the fact that there are a lot of data changes in my application, I am thinking to improve the painting of the BufferedImage. Most of the bar chart remains the same. It is just shifted to the right and the latest data changes are added to the left of the bar chart.

At the moment the whole BufferedImage is recreated out of the data stored in the buffer. What I could think of is to shift the old BufferedImage using AffineTransformation and only add the recently added data. This would enormously decrease the amount of drawing operations on the BufferedImage.

But I do not know if this will speed up the application. How expensive is the AffineTransformation on a BufferedImage?

Any remarks are welcome. Also some other hint how to create a performant swing application.

Thanks in advance

mKorbel
  • 109,525
  • 20
  • 134
  • 319
hami
  • 443
  • 5
  • 13

1 Answers1

1

Without some sort of baseline, it's very difficult to measure improvement. At a start, you might compare the two approaches shown here using JFreeChart. The DynamicTimeSeriesCollection loafs at 10Hz; I haven't examined the other closely, but it looks flexible.

Community
  • 1
  • 1
trashgod
  • 203,806
  • 29
  • 246
  • 1,045
  • I played already a little bit with JFreeChart, but I seemed not to be the right choice. The application should look similar to an existing one. So I started to get into JFreeChart and make adjustment. But I just need only a very simple chart, so I thought designing an own component would be more performant and also more flexibel. – hami Jul 02 '12 at 15:42
  • I've gone that way occasionally, but always return for scalability. It's _much_ easier to change features and add new charts. Odd thing about charts: nobody wants just one. YMMV. I'm still curious about the load and duty cycle. – trashgod Jul 02 '12 at 15:57