Market NinjaMarket Ninja

Why is Parsing Slow?

The main data collection mistake: how to avoid background window throttling and speed up parsing.

When collecting large volumes of data (for example, during bulk link parsing or exporting thousands of reviews), you may notice that the process slows down or stops entirely. This is most often caused by fully hiding the Market Ninja extension window. This is not a parser error — it is a built-in optimization mechanism in modern browsers (Chrome, Yandex, Edge).

Why does this happen?

To save battery life and computer resources, browsers apply a Throttling mechanism (artificial slowdown) to invisible windows.

If you click the "Minimize" button (the minus in the corner) or completely cover the extension window with other applications, the browser decides: "The user isn't looking at this program right now, so its work can be paused." As a result, Market Ninja's data collection speed can drop dozens of times, and the parsing process can stretch on for hours.

The main rule: never minimize the extension window or cover it 100% with other application windows.

How to parse correctly in the background?

To keep Market Ninja running at full speed while you work on other things (for example, building reports in Excel or watching a video), follow these simple rules:

1. Keep the extension window partially visible

Instead of minimizing the parser window, simply make it smaller and move it to the edge of the screen. Another application's window can be open on top of it, but the key is that at least a small part of the extension window remains visible on your monitor (even a strip of a few pixels). As long as the window is physically rendered on screen, the browser will not throttle data collection.

2. Use a second monitor

If you have multiple monitors, simply drag the Market Ninja window to the secondary screen and leave it there. This is the most convenient and reliable option for working with large exports.

Interested in the technical details? You can read about the mechanisms for throttling invisible windows in the official developer documentation: Chrome Page Lifecycle API and Intensive Wake Up Throttling.

Last updated

On this page