You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I load a C3 chart using the below code, it seems to be taking up a lot of CPU usage. It all stems from the c3.generate() call.
I'm assuming the library is looking for browser resize/interaction updates. (Screen shot attached, where in Chrome the tag is constantly being updated/scanned.)
In my case, I only need to draw the chart but not do anything else. (I do have a lot of data points to work with.)
Is there a way to improve performance, perhaps by disabling this C3 behavior?
The text was updated successfully, but these errors were encountered:
This is possibly a duplicate of #926, but unless you're calling generate() a lot, it's probably a separate issue.
Clearly there's something wrong with how C3's listening to the resize event. We really need to create a task force to troubleshoot the current spate of performance issues before they get any worse. See Google Group discussion.
Any suggestions and/or pull requests you can offer are very welcome.
@ryankicks Sorry for the late response. I think resize_auto = false can be used. This option was introduced by this PR #860 and it's still rc version (0.4.11-rc2), but it will be release shortly.
@masayuki0812 resize_auto = false doesn't work. In the "loadConfig" function, the key is splitted by "_" and the "find" function don't find the "resize" so it keeps the "true" value of the default config.
After I load a C3 chart using the below code, it seems to be taking up a lot of CPU usage. It all stems from the c3.generate() call.
I'm assuming the library is looking for browser resize/interaction updates. (Screen shot attached, where in Chrome the tag is constantly being updated/scanned.)
In my case, I only need to draw the chart but not do anything else. (I do have a lot of data points to work with.)
Is there a way to improve performance, perhaps by disabling this C3 behavior?
The text was updated successfully, but these errors were encountered: