Pure Javascript Charts's Javascript Working Time

[Simple.Chen]

I wonder the pure javascript chart 's script working time.

If the javascript working later than any other html element in the page or not ?

I mean the script to structure the pure javascript chart.

waiting for your replay...

 

[Simple.Chen]

Another question about the pure javascript chart

How i can calculate the cost of time about structuring the pure javascript chart ?

 

 

[Simple.Chen]

Another question :

What are the factors that would affect loading time of the pure javascript chart?

[Guest Sumedh]

Hi,

 

The factors which can affect loading time of charts are,

 

> Number of data-plots

> System RAM.

 

Suppose if you try to plot 500-600 data points, then chart will take time to plot the data.

 

System RAM also affects the loading time chart, as the charts render in browser's sand box.

 

To check loading time of chart, you can check it in the Network tab of the browsers console.

[shamasis]

Here we go...

 

For pure JS charts, FusionCharts loads approx 30% of its codebase during page-load (before "onload" provided the scripts are in page head.) The rest 70% is loaded when a chart is instantiated. This latter dynamic script loading depends upon the chart-type being loaded. This dynamic behaviour can be altered by simply including the required scripts in page head. Thus, entire 100% of script can be made to load during page-load.

 

Could you elaborate as to what you mean by "cost of time about structuring the pure javascript"? If you mean the time to load and execute/initialize the library... it depends upon your network and client bandwidth. However, once the files are loaded, reloading takes no time since the files are cached. The framework initialization time is approximately 100 ms for first 30% and 500ms for entire 100% on a standard 2Ghz 4GB system (however, this benchmark will widely vary from system to system.) Otherwise, if you mean the time taken to render a chart, it varies on a large number of factors. You should ideally set an acceptable time limit for yourself to render a chart and then render the chart that for your use-case is the heaviest, and try it on a really slow/mobile system and check if it meets your eye.