Updated today to latest snap - very slow
-
-> stephenw10, indeed I am running the NanoBSD version.
I've tried running the commands from ssh, mount_rw was instant, mount_ro took around 20 seconds.Does this seem to point to the problem then? Does anyone know of a workaround?
-
Is this the only snapshot any of you have tried?
It would be useful to try and get some idea when this problem was introduced.
I'm not running 2.1 at all currently but the last snapshot I tried, some months ago, did not exhibit this behaviour.Steve
-
Things are smooth/snappy on my ALIX with a snapshot from today, I've not seen this slowness myself. Saving does take about 6-7 seconds but it always has on ALIX.
Using HTTPS to get to the GUI, everything seems happy.
-
I'll update to the latest in 10 min, but this version from last night is already 30 seconds on the Traffic Shaper Wizard's first "Next".
ā
On Latest : built on Tue Apr 17 12:13:03 EDT 2012
simple test using latest Chrome browser 18.0.1025.163
- System Advanced -> (select) -> Enable Secure Shell -> Save
3 minutes, 23 seconds for it to return
I revert the change and Save
3 minutes, 31 seconds for it to return
I think I will test another browser, just in case.Ā Then I may disassemble the Alix, remove the flash card and re-install the 2.1 as a test again.
-
I did that same test on my alix on the same snapshot, ~16 seconds to enable/disable SSH. Though I'm in Firefox, not that it should make that large of a difference.
-
this maybe largely dependent on the speed and quality of the CF card.
I have a CF card in one of my Alix systems that will timeout any attempt to upgrade the firmware because the 4GB CF card is just so bad.
-
Agreed,
though here we are comparing performance from 2.0.1 stable to 2.1 on the same hardware. On 2.0.1 everything was lighting fast. On 2.1, routing / firewalling performance is good, the only problem is when changing settings.
-
Whilst I agree that the speed of the card will make some difference I have a hard time believing that any card should take over 3 minutes to remount.
I have never detected any difference between cards of wildly varying 'quality' with regards to boot time or remounting. Since NanoBSD disables DMA they all run at PIO speeds anyway hence '133X' or '300X' claimed card speeds are irrelevant.Is 2.1 still disabling DMA correctly? Does it need to for FreeBSD 8.3?
Any power saving 'spin down' type options enabled?
Steve
-
Is 2.1 still disabling DMA correctly? Does it need to for FreeBSD 8.3?
That hasn't changed
Any power saving 'spin down' type options enabled?
No, in fact we actually force APM off now since otherwise some silly HDDs will kill themselves with load cycles. (But that's only done if the drive reports that feature as supported)
Either way - those two types of things would be fairly universal, they would affect everyone. It wouldn't be fast for me and slow for you.
-
Agreed.
Perhaps a combination of pfSense and BIOS options then?
Though that wouldn't account for introducing the problem by simply switching to 2.1.
Config slice become corrupt or fragmented somehow?Ā :-\Steve
-
Looking around in /boot/loader.conf defaults againā¦ I'm no BSD expert by a longshot, I've read that increasing the kmem size reduces the change of a kernel panic.
vm.kmem_size="435544320"
vm.kmem_size_max="535544320"That size looks like 415Mb, and my firewall is running with 256Mb of RAM, could it be related??
-
Sorry for the late reply, but working on the Alix meant I had no Internet.
Tests were done:
- zero the 4GB card, re-image 2.1 from yesterday, re-testĀ :Ā same sluggish results
- take the 2GB card that came with the units, image it with 2.1, re-test : same result
- re-image 4GB card with 2.0.1 : smooth as butter, fast.Ā 9 seconds to enable SSH, 8 seconds to disable
I posit something IO related is very wonky.
Sadly, until my 2nd Alix is back in my hands, I shall have to remain at 2.0.1
-
Hello!
Tested with ALIX.2 v0.99h board and 8GB CF and got the same results as barista:
"Build on Tue Apr 17:30:20 EDT 2012" - DHCP on WAN interface does not work, setting up something takes forever (some minutes to get a respond)
connected via serial console running top - system is idle but I tried to reboot via Web-GUI and tried to start top via serial console and I was not able to start top. Looks like the system got hung for minutes then get back to normal work (top starts in console and I got the shutdown message but the system does not shutdown so I unplug the power).After reboot I switched the slice (lasting for minutesā¦) I rebooted (once again waiting minutes ...could not wait ... unplugged power)
"Build on Mon Apr 16 08:51:47 EDT 2012" - WAN got an IP via DHCP but changing configuration takes a long timeboth builds take a long time to configure WAN but the damaged takes a lot longer.
At the moment im updating to "build Wed Apr 18 18:57:19 EDT 2012" - reporting later.
Bye,
eweri -
Timings from 2 of my Alix 2D13 256MB systems for "mount -uw /" and "mount -ur /":
a) 2.1-DEVELOPMENT (i386)
built on Wed Mar 28 20:25:36 EDT 2012
FreeBSD 8.3-RC2
Both mounts are quick (0:00.04 then 0:01.27)b) 2.1-DEVELOPMENT (i386)
built on Mon Apr 16 16:52:53 EDT 2012
FreeBSD 8.3-RELEASE
"mount -uw /" is quick (even reporting 0:00.00)
"mount -ur /" is always around 1:02.00 (4 samples between 1 minute and 1:05.00)I also tried "mount -ufr /" in tghe hope that the "force" flag might make force something to close that was accidentally open or whatever, it made no difference to the timing.
Is this a feature of 8.3-RELEASE?
Can others confirm if the issue is only on 8.3-RELEASE builds?
-
Okay here are my results with "build on Wed 18 18:57:19 EDT 2012":
WAN does not get an IP-address via DHCP, configuration changes takes a very long time to complete.
I tried to reboot via Web-GUI and this is what i got from serial console (it hung for a long time):
Apr 19 09:45:43 init: timeout expired for /bin/sh on /etc/rc.shutdown: Interrupted system call; going to single user mode
Waiting (max 60 seconds) for system processvnlru' to stopā¦donep Waiting (max 60 seconds) for system processbufdaemon' to stop...doneĀ Ā Ā Ā
Waiting (max 60 seconds) for system process `syncer' to stop... shHope this helps,
eweri -
: cat /etc/version 2.1-DEVELOPMENT : cat /etc/nanosize.txt 4g : cat /etc/version.buildtime Tue Apr 17 06:39:44 EDT 2012 : uname -a FreeBSD alix.pingle.org 8.3-RELEASE FreeBSD 8.3-RELEASE #0: Tue Apr 17 06:39:26 EDT 2012Ā Ā root@FreeBSD_8.3_pfSense_2.1.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386Ā i386 : time mount -uw / 0.000u 0.006s 0:00.00 0.0%Ā Ā Ā 0+0k 0+5io 0pf+0w : time mount -ur / 0.005u 0.015s 0:01.76 0.5%Ā Ā Ā 64+2680k 0+578io 0pf+0wDHCP WAN works fine for me, as does IPv6 and such.
What packages are installed on the ones having issues? I have none installed.
-
Update or fresh install might be pertinent here.
Steve
-
That's possible. I've got a ton of CF's around, I'll image a new one and swap it in, see what happens.
-
My test system with 8.3-RELEASE also had Squid and SquidGuard packages running. For some reason, between "Configuring WAN interface" and "Configuring LAN interface", Squid processes would start. Then later the package startup would also start Squid. There is some sort of double-startup of Squid with the current 2.1-DEVELOPMENT and whatever is happening with the PBI installation process - I will look at that later and start another thread for it.
I removed SquidGuard and Squid.
Now "mount -uw /" is instant (as always) and "mount -ur /" is about 2 seconds.
My 8.3-RC2 snapshot didn't have any packages installed, so that seems to be why it is fast to mount read-only.
After adding packages (at least PBIs like Squid/SquidGuard) the time to mount read-only increases substantially.
-
The freshly imaged card was indeed much slower, taking ~30 seconds to mount ro for me.
I don't think it's FreeBSD 8.3 in general though, there were other changes made to how the nanobsd images are generated which could be contributing.
