Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizKindly log in to use this feature. We’ll take you to the login page automatically.
LoginMobile Technologies Mobile Computing 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
_x000D_ Make sure that it's actually Chart.js / Firefox that is causing the problem (try it out on other browsers, put a stopwatch right before you call new Chart... and stop it in onAnimationComplete) While the following steps suggestion should logically reduce the number of calculations, I couldn't see much difference (the chart rendering completes in 0.5 seconds on both IE and Firefox with animation turned off and 7-8 seconds with animation turned on for 800 datasets with 10 points each) If you are aware of your data range (or if you can calculate this efficiently on the server side), you could override the scale and set your own scale ... scaleOverride: true, scaleSteps: 10, // or whatever suits your dataset better scaleStepWidth: 1, // or whatever suits your dataset better scaleStartValue: 0, // or whatever suits your dataset better ... It might also be a good idea to turn off tooltips if you haven't done so (with 800 data sets, any tooltip you have is not going to be that useful) ... showTooltips: false, ...