2.3 firewall tab -rules slow

Steve_B

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.

maverick_slo

Ok I will do it if you already ask for it :)

maverick_slo

BTW, if we nail it, you owe me a bear, lol :)

maverick_slo

Funny…

I just did it, page loads exactly the same amount of time.

nocss.PNG_thumb

Steve_B

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.

jwt

Pingle seems to have a handle on it (Internal communication)

Steve_B

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.

maverick_slo

Yup, thats it :)
Now they're flyin :)

Steve_B

OK cool. Thanks for doing that.

There is an issue reported in Firefox where initializing the sorting is extremely slow. Trying to find a work-around now.

Steve_B

I have just pushed a work-around for this. Would you please gitsync and try it when you have time?

maverick_slo

Hi!

We can close it :)

Chrome is fastest, IE and FF little slower (1.3sec load time) which is excellent :)

Steve_B

Yay!

Thanks to everyone who helped to track this down and test the fix. I learn something from you guys every day :)