32-bit 2.2 webConfigurator hangs
-
Cutting a long story short, my 32-bit main system is running just fine on 2.1.5 . I upgraded it to 2.2 but had to rebuild it with 2.1.5 to get some stability back.
My test box had exactly the same problems as soon as it was upgraded to 2.2 Release. It was fine on daily 2.2RC builds. I rebuilt my test box on 32-bit 2.2 Release with Snort and Squid3 installed individually from the packages menu. I have come to the conclusion that 32-bit pfSense 2.2 on 1GB RAM is unuseable. It may work without any packages but I need Snort and Squid so I am moving up to 64-bit on some recently acquired kit from a recycler.
I have fond memories of 8-bit computing, 16-bit, and now 32-bit.
R.I.P 32-bit pfSense, you served me well. Thank you.
-
It's gonna be exact same unusable when you dump huge resource hogs like squid and snort on a 64bit system with 1GiB of RAM. (On the contrary, 2.2 is a whole lot more usable on systems with very limited amounts of RAM.)
-
It really depends on the bandwidth being pushed through the firewall, I think. I have a 2.1.5 rig running i386 dual-core VM w/2GB, Squid, SquidGuard and the usual reports/graphs packages. Runs like a top 99.9% of the time. CPU usually sits at around 2-3% and RAM is 34%. However, if I start pumping 100Mbps through it, the CPU spikes to 90+% and all my vSphere alarm bells go off.
-
It's gonna be exact same unusable when you dump huge resource hogs like squid and snort on a 64bit system with 1GiB of RAM. (On the contrary, 2.2 is a whole lot more usable on systems with very limited amounts of RAM.)
My new 64-bit machines are dual core with 4GB RAM installed but I'm thinking about maxing them out with 8GB.
My own personal experience of pfSense has shown me that:-
32-bit pfSense 2.1.5 on 1GB RAM with Snort and Squid was (and still is) reliable and perfectly capable.
32-bit pfSense 2.2RC upgraded from 2.1.5 on 1GB RAM with Snort and Squid was equally reliable.
32-bit pfSense 2.2Release on the same hardware… too many wasted hours trying to get it working reliably.Why wait for 32-bit 2.2.1 if the developers don't develop on or use 32-bit pfSense anymore?
-
I'm not suggesting your should wait for anything. What I'm suggesting is that when you plop 64bit on the same inadequate HW there's absolutely not gonna be any improvement regarding performance. Saying that 32-bit pfSense 2.2 on 1GB RAM is unuseable is a non sequitur.
