If you notice an extremely low fps (frames per second) on the Cryptowatch chart, your browser may be misconfigured.
This is probably due to hardware acceleration being disabled for HTML5 canvas. Enable it and restart your browser.
1. In a new tab, open
2. Make sure
3. Restart Firefox
You may also have to set
true. Read more.
Incidentally, Firefox 57 introduced an update which can dramatically speed up page rendering. Upgrading to Firefox 57 might be a good idea.
Lastly, we notice that in general Google Chrome has an easier time hitting 60fps when scrolling/moving the cursor. We recommend Chrome over Firefox.
1. Open Chrome Settings and find Advanced > System
2. Make sure "Use hardware acceleration when available" is enabled
3. In a new tab, open
4. Make sure "Accelerated 2D canvas" is enabled
5. Restart Chrome
If the chart and interface are not lagging but Cryptowatch is consistently using a lot of CPU (50% or more), you can try a few things:
1. In the settings panel, throttle the refresh rate
2. Draw fewer indicators or make candles wider
3. Run fewer Cryptowatch tabs
4. Buy a better computer...sorry.
If none of the suggestions above help, you can reach out to us with some diagnostics to get some help. It's possible you've stumbled across a bug or inefficiency in our code that is causing the issue.
First, you will need to record a performance profile while Cryptowatch is open.
To record a performance profile in Chrome:
Click the options menu in the top-right of a Chrome browser page. Then go to
More Tools >
2. You will see a window like the one below. Select the Performance tab.
3. Click the record button (the circle) to begin recording the profile.
Stop after a few seconds and you will receive a readout like the one below.
5. Save the profile by clicking the Save Profile arrow, just below the Elements tab.
Finally, find the saved profile file in your downloads folder and email it to email@example.com along with the following details:
Which browser(s) you're having problems in
Which URL(s) exhibit the problem
How consistently the problem happens (occasionally? every time?)
How long the Cryptowatch session is open before the problem starts (after a few days? immediately?)
Our developers can use this profile file to better understand where the bottleneck is and fix the inefficiency.