Setting up Cryptowatch
Extensibility and Community
API

Troubleshooting performance issues

Experiencing performance issues? This document outlines the most common problems and potential solutions for different browsers.

Laggy Chart

If you notice an extremely low fps (frames per second) on the Cryptowatch chart, your browser may be misconfigured.

Cryptowatch may prompt you to enable "Accelerated 2D canvas" to remedy poor rendering speeds.

This is probably due to hardware acceleration being disabled for HTML5 canvas. Enable it and restart your browser.

In Firefox:

1. In a new tab, open about:config

2. Make sure layers.acceleration.disabled is false

3. Restart Firefox

You may also have to set layers.acceleration.force-enabled to 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.

In Chrome:

1. Open Chrome Settings and find Advanced > System

2. Make sure "Use hardware acceleration when available" is enabled

Open Chrome settings and go to Advanced > System > "Use hardware acceleration when available".

3. In a new tab, open chrome://flags

4. Make sure "Accelerated 2D canvas" is enabled

Enable "Accelerated 2D canvas" in chrome as well.

5. Restart Chrome

High CPU Usage

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 order book refresh rate

2. In the settings panel, make sure "animate feeds" is disabled

3. Draw fewer indicators or make candles wider

4. Run fewer Cryptowatch tabs

5. Buy a better computer...sorry.

How to record a performance profile in Chrome

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:

  1. Click the options menu in the top-right of a Chrome browser page. Then go to More Tools > Developer Tools.

Go to Chrome Settings > More Tools > Developer Tools (or click F12).

2. You will see a window like the one below. Select the Performance tab.

The Performance tab is in the top of menu bar of the Developer Tools window.

3. Click the record button (the circle) to begin recording the profile.

Click the record (circle) button in the middle of the Developer Tools window.

4. Click Stop after a few seconds and you will receive a readout like the one below.

A performance profile recording.

5. Save the profile by clicking the Save Profile arrow, just below the Elements tab.

Save your performance profile with the downward-facing "Download" button, near the menu bar.

Contacting Cryptowatch support

Finally, find the saved profile file in your downloads folder and email it to troubleshoot@cryptowat.ch 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.