Using cache

Downloading data with cache

By default caching capabilities are disabled.

In order to enable them, set useCache flag to true and optionally specify the cacheFolderPath (default is .dukascopy-cache).

All the binary artifacts (which are downloaded from the dukascopy servers) will be stored on disk, and all the subsequent requests with similar instruments and date ranges will no longer be downloaded from those servers, and will be fetched from the file system instead.


via CLI:

npx dukascopy-node -i eurusd -from 2021-02-01 -to 2021-03-01 -t m1 -f json --cache

or via Node.js:

const { getHistoricalRates } = require("dukascopy-node");
 
(async () => {
  try {
    const data = await getHistoricalRates({
      instrument: "eurusd",
      dates: {
        from: new Date("2021-02-01"),
        to: new Date("2021-03-01"),
      },
      timeframe: "m1",
      format: "json",
      useCache: true,
    });
 
    console.log(data);
  } catch (error) {
    console.log("error", error);
  }
})();

After running, you can see that dukascopy-node has created the cache folder called .dukascopy-cache and stored the downloaded artifacts there.

If you run the same code again, then you will notice that it's faster, since the data comes from your local disk rather than from network.

First run (populating cache) - download time - 5.9s

dukascopy-node cache

Second run (using cache) - download time - 163ms

dukascopy-node cache