Jump to content
Software FX Community

Chart FX 7 loading time


Aarthi
 Share

Recommended Posts

Hi,Well, actually the performance is related to the complexity of the chart being displayed, for example a Curve chart is much slower than a Line chart, Circle markers are slower than Squared ones, in general, we depend on the performance of GDI+ so the performance of the chart depends a great deal of the performance of the GDI+ primitives used. Performance of charts vary widely based on datasources used, data size (the number of points is an important thing you need to consider when rendering charts, it is recommended to keep it under 70.000), data population methods, visual features, chart size, etc. While it is true that many development tools and web development technologies significantly reduce development time and allow for quicker deployment, this paradigm presents a whole new challenge for developers; among them, server scalability and performance. The real issue in web application design is user experience. To make an application perform as a traditional desktop application when it is actually a distributed application that could be simultaneously servicing hundreds or even thousands of users. To understand how Chart FX impacts server performance, consider every time a web page containing a chart is accessed, the Chart FX Server component creates a chart in memory using a device context created on the server. Therefore, hardware and software settings on your server affect how quickly these charts are created. In general, Chart FX performance depends to a great extent on the chart format generation (Image, .NET Control, SVG, Flash, etc) and the chart return mechanisms (GetHtmlTag or GetHtmlData) chosen. Also, when generating chart images you should pay close attention to the Chart FX default settings and chart size as major performance factors when the server is under a heavy load. For example, 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. Chart FX was designed to conform to web development guidelines and to take advantage of the server-bound nature of web applications. Nevertheless, many of the product's default settings are tailored for improving the chart's look rather than focusing on server performance. In situations where Chart FX is heavily used, these default settings may need to be configured to improve performance. For example, Chart FX uses a default smoothing algorithm (anti-aliasing) on text and markers that negatively impacts server performance. This feature can be turned off by using the SmoothFlags property to

Link to comment
Share on other sites

Thanks for your reply.

We are trying to load a chart control without any data and without any features. For rendering that chart image, run time is taking more than 8 seconds. We would like to know what are the configurations that can be done so that we could reduce this loading time

Is there any way to reduce the number of server validation steps for chart fx?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...