[performance] slow population of the menu if many requests

[myrdd]

The menu needs too long to open when there've been many requests since the last reload. This is normally due to ajax requests, which can best be tested on a maps site after some scrolling / moving around. At ~800 requests, the menu needs one second on my laptop.

[nodiscc]

I may argue that can be considered a bug in some cases. For example, when using my feed reader (TinyTiny RSS) - which does a lot of requests because feeds embed items, and it's refreshed regularly - the menu takes about 15 seconds to open on my laptop (Intel Core i3-3217U @ 1.80GHz; 4GB RAM), freezing the whole browser UI.

This happens even when blocking is disabled. Using tt-rss with RP completely disabled is also much faster. Unfortunately I can't disable it just on my feed reader because 1. It's impossible to disable RP on a per-site basis 2. path-based rules are not implemented.

So, serious bug or not? RP is supposed to make browsing faster, in this case it has the opposite effect.

Attaching a screenshot. At this point the feed reader was so slow it was unusable. I had to reload the page.

[myrdd]

Wow, I'm sorry for that @nodiscc! I agree this is a bug.

This happens even when blocking is disabled.

Yes, because even in that case all requests are recorded.

1. It's impossible to disable RP on a per-site basis 2. path-based rules are not implemented.

I think that path-based rules wouldn't change anything in your case. In fact I can think of the following countermeasures: a. improve efficiency b. record less data, for example, diable counters on a tab or for specific sites

By the way, there might be the following workarounds for you

• Disable the request counters
• Reload the page as soon as it gets too slow

Again, sorry, I can see this is a severe issue, so I'll mark this issue as important.