WebGUI very slow page load
-
I'm running on Sempron 140, 1GB ram.
CPU are always below 5% use, and RAM below 15%, so i don't think is a hardware issue.
statics DHCP leases are 100+ but no corruption in here.
It's slow even on showing floating rules, you can see entry by entry rendering, I think it takes 500ms (or more) to render a row, so with 100+ entries the entire page takes a minute.
I can give you remote access if you need so.
-
If it is JavaScript I wouldn't expect to see an increased load on the server side, it may be overloading the browser or the PC/VM used to browse.
Any way I could get a copy of your config.xml with that many entries to try? You can strip it of any identifying information, and mail it to me privately, jimp (at) pfsense [dot] org.
-
The browser doesn't show any sign of high CPU load.
It's also happens on Floating rules on firewall. You can see row by row render of the rules.
I emailed to you the config.xml. -
I am not seeing any speed issues whatsoever with that set of DHCP static maps or floating rules.
Both loaded instantly when viewing those pages, no discernible delay at all.
-
I'm using Oct 14 snapshot, anyway there is a debugging or logging feature that can be the cause of the slow down?
-
Hard to say for sure, but you really should update to something current.
-
Just made some testing on todays snapshot and it's working quite well on a sempron with 512Mb of Ram, i did several tests on DHCP. in web gui.
Please download the latest snapshot, and what the dev team always say: DO NOT USE THE 2.0 on PRODUCTION!
-
Just made some testing on todays snapshot and it's working quite well on a sempron with 512Mb of Ram, i did several tests on DHCP. in web gui.
Please download the latest snapshot, and what the dev team always say: DO NOT USE THE 2.0 on PRODUCTION!
I've almost a year of using 2.0 in production. It's very stable with my configuration!
I think that someone has to do 2.0 on production for real world testing and bugreports and that's what I'm doing here to the best of my abilities!Anyway I'll update the snapshot and re test it.
-
Using 2.0 in production is OK lately, with due caution. The warnings everyone sees are from the days of Alpha-Alpha when it really was rather unstable and prone to destruction. It's mostly OK at the moment but we have had some patch issues the past couple weeks as we try to tackle the remaining few bugs that are holding us back from RC1.
-
Updated to latest (23 dic) snapshot and works fine.