A common practice among web developers is to create a big chart that can be easily read on a browser. However, this practice can be an important factor on how your server behaves and performs under heavy load. Essentially, a bigger chart means a larger image that needs to be processed, generated, stored and finally downloaded. This affects in one way or another, the application's overall performance, therefore, you must be careful when choosing the final chart rendering size in the page if server performance is a concern.

To illustrate this, suppose you increase the size of a 400x300 Png image of a
chart and measure its impact on server performance.
We found that for every 30% increase on the chart width and height, the server
experienced a significant decrease in the number of Requests per Second it
could process.
Changing the chart size may be costly on your overall page design. However, it
may be an excellent source to boost performance if you have exhausted all other
options.
While reducing the chart size considerably will benefit server performance, you
must be careful not to select a size so small that will compromise the chart's
readability.
|