2.3 firewall tab -rules slow
-
And this is what I see on Firefox 44, Win10
Page loads/renders 7-9 seconds…
-
Can you expand DOM.event handler please?
-
Sure.
Reallllly long picture :)
-
Perfect. Thanks.
So now we know it is spending all that time recalculating the style of something or other!
Would you experiment with the different CSS files please and see if that has any effect?
System->General setup->Theme
Being of a light and sunny disposition, I prefer pfense-Beta, but perhaps you use something else.
-
I already tried it and no luck.
Tried all 3 of them.
Interesting sidenote…
Chrome on android 6 displays it in 2 seconds.
I think my computers have something in common will investigate that too... -
Removed antivirus same thing.
I don`t get it anymore :) -
I literally clicked through ALL pages and only this one is superslow.
NAT for example is very fast and it has lots of entries. -
Nor me. I have 25 rules and the page loads in 380 mS according to the Chrome profiler.
Tough without being able to reproduce it.
-
Maybe is this specific issue limited only to my firewall…
I did upgrade a lot from 2.X to every version until today... -
In latest tests on fresh win 10 only firefox is problematic, ie, chrome, opera all load page in less than 2 seconds only firefox takes 8 :S
-
FWIW I also have the slowness problem in Firefox (Currently 44.0) and not in Chrome/Safari. For me it takes about 16 seconds total for the main WAN rules to finish the first time. I have the Firefox Web Developer Performance Profiler (Shift F5) .json export that you can import into your Firefox and see for every line where it spent the time but it is 1.8 MB and .json files won't attach here. For instance one of the most plentiful entries is "Recalculate Style" and if you select it, over on the sidebar you see the files it was processing such as pfsense.js:187
Here is a screenshot of that:
-
Yeah we have same problem :)
-
We have tried everything we can to reproduce this, but no luck so far. Were I able to reproduce it, I would probably troubleshoot like this:
From the command line, or from Diagnostics->Command prompt, create an empty CSS file:
touch /usr/local/www/bootstrap/css/empty.css
Now from the System->General setup page, change the web configurator theme to "empty" and save.
The screen will now look horrible, but it will still be functional. You wont have a menu any more, but you will have links you can click on, so click firewall_rules. Does the page load more quickly? Much more quickly?
If it is improved, I would go back to the pfSense theme (have to click the general setup link), copy the pfSense theme:
cp /usr/local/www/bootstrap/css/pfSense.css /usr/local/www/bootstrap/css/pfSense-TEST.css
now select that pfSense-TEST theme from the setup page. You can now start commenting out sections of the pfSense-TEST.css file to try and locate the culprit. Probably best to start commenting out from the bottom up :)
I'm not asking anyone to do this or even suggesting that it is a good idea, but it is about all I can think of at this point.
-
Ok I will do it if you already ask for it :)
-
BTW, if we nail it, you owe me a bear, lol :)
-
Funny…
I just did it, page loads exactly the same amount of time.
-
OK good. So we know it is not related to the pfSense CSS then.
Thanks for taking the time to do that.
I'll suggest the next step shortly.
-
Pingle seems to have a handle on it (Internal communication)
-
Let's try this please:
Diagnostics->Edit file
Browse to /usr/local/www/firewall_rules.php
GoTo line 889 using the GoTo control in the top right
Comment out the code that makes the rules sortable:
events.push(function() { /* // Make rules sortable $('table tbody.user-entries').sortable({ cursor: 'grabbing', update: function(event, ui) { $('#order-store').removeAttr('disabled'); reindex_rules(ui.item.parent('tbody')); dirty = true; } }); */Obviously the code will no longer be sortable, but lets see if it loads faster.
-
Yup, thats it :)
Now they're flyin :)