Memory usuage after reboot
-
@abailey10 said in Memory usuage after reboot:
No one else has this problem or even notice it? ....
What ? I missed something ?
Using a bare bone, retired desktop PC with : an Intel(R) Pentium(R) 4 CPU 3.20GHz - 2 CPUs: 1 package(s) x 2 hardware threads
(2 WAN, 3 LAN, some 20 devices on LAN and a boatload of captive portal users )
@abailey10 said in Memory usuage after reboot:
Also dsl reports speed test has random spikes up to 2000ms down and upload as it cant keep up clearing the queue
This one http://www.dslreports.com/speedtest ?
Just tested :
That's a less general discussion, and has it's own forum here.
@abailey10 said in Memory usuage after reboot:
as it cant keep up clearing the queue
What queue ?
The spikes can be removed, that's no a big issue.
What stays : your LAN's are probably much faster as your WAN-to-the-Net-connection.
So, pfSense will buffer while your uplink is being pushed to the max. Upstream signal 'converters' like cable or ADSL modems also inject there part of delays. -
@Gertjan Lets stay to the point, the speed test was just to show performance drop at some point the gateway's access time spikes and the test show random high spikes happens on downloads only. The point is 18 percent memory on first install and everything works great. After rebooting pfsense it only uses 7 percent memory and the gateways have high access times and download has random spikes again.
And by the way this network card has two hardware queue's 1 per port.
-
@abailey10 Im using fx 4100 3.6ghz quad core , 4gb ddr3 1333 cas 9, 2 port intel pro 1000pt, network card is plugged into pcie 2.0 x16.
This wasnt a problem on earlier builds, but has been for the last several. As long as i never reboot after update it uses 18 percent memory again and all works great.
-
Mmm, I think the memory usage you are seeing there is probably not directly related to any slowness you're seeing.
2000ms ping spike are obviously an issue. If that's actually caused by the firewall I would expect to see a big CPU spike recorded at that time. I have seen systems present like that if they get stuck in a filter-reload loop on occasion. You would see that in the system log though.
If it's something else upstream it might cleared by re-connecting the WAN or rebooting your modem maybe.Steve
-
pfsense seems to have memory issues, i tired 3 other firewalls including opensense , they all work without this issue.
-
@abailey10 I would just use something else then.
-
pfSense is the factor that we all have in common : version 2.4.4-p3.
Believe me, it's all identical code for all of us.Difference are :
Hardware - and thus (FreeBSD) drivers used.
Installed packages ...
An last but not least : settings.Yet, you draw this conclusion :
@abailey10 said in Memory usuage after reboot:
pfsense seems to have memory issues,
Let say you ommitted two words :
... for me
-
@abailey10 said in Memory usuage after reboot:
pfsense seems to have memory issues, i tired 3 other firewalls including opensense , they all work without this issue.
Yeah... right... not. Besides every freaking web service out there being lower on memory after a restart, your conclusions with 1 (your) testcase is simple lopsided. If the software stack itself had memory problems that would have rang alarm bells all over the place for a multitude of people. Don't you think? So it's down to the list @Gertjan wrote: HW, installed packages and mostly your configuration (base & packages). Simple as that.
Also if you want to get to the bottom of your usage, try
topwithshift+mto sort for processes that have the most memory allocated or do someps axwwwetc. output before and after your "too much memory in use" condition to check who the culprit eating your RAM may be.But with years almost two decades of web application hosting knowledge I have to say that everything that either doesn't run into a memory leak draining memory until swap (would be seen eating your memory until 100% in use) or is a wrong configured host/services that simply allocates far too much memory is simply normal. Anything being it the OS, webserver, services etc. may reserve some memory if it is readily available. So pages like https://www.linuxatemyram.com/ don't come from nowhere. We always have people asking where their RAM went and always have to make them acknowledge, that it isn't something bad. OK we're using BSD here, but never mind that :)
-
watching the top the first thing that come to my mind... could be related to unbound that restart with dhcp registration if you see mem go up and down ?
-
Perhaps. As we don't have a complete
psoutput and don't know which packets are in play, something like pfB-NG could very well add a big dent into unbounds RAM usage. But that's all speculation until a much more in depth look can be done with more intel about the system and installation as well as additional packages. -
From my understanding, he's complaining that it's not using enough RAM. Says it's slow after reboot until the system gets cached. Whatever, I think it's a non-issue. DSLReports speedtest issues can be anything from ISP to modem.
-
Yeah the memory usage might possibly be a related symptom but it's not a cause here.
It's almost certainly CPU usage causing those ping spikes. Check the system log like I suggested earlier. If some process is triggering it you should be able to see that firing when you see the ping issues.
Steve
-
I thought pfsense ran from ramdisk once loaded from ssd. If so then why would 50 percent lower memory usage not be a red flag. Its not cpu spikes as it has never been past 20 percent during high load and gui with monitors usually never see more than 1 to 6 percent. This could be hardware related, except if i get an update and it reboots memory usage will be 18 percent which is normal not 7 percent. My internet is 100 down 10 up, no way its stress a quad core at 3.8ghz without power savings of any kind or turbo , this cpu is not power or heat throttling. Its like pfsense cant load all of itself into the ramdisk after reboot
-
Please understand that this is a problem you and you alone are experiencing. It might take some time to determine what is peculiar in your environment. Especially on an internet forum from remote locations given little information.
It might just be that pfSense doesn't run well on your specific hardware.
-
@abailey10 said in Memory usuage after reboot:
I thought pfsense ran from ramdisk once loaded from ssd. If so then why would 50 percent lower memory usage not be a red flag.
No it won't if you haven't told it so. There was the old nanoBSD version, that was pre-configured to run with ramdisk support but that is old news and if you didn't set up the ramdisk under System > Adv. Settings it will not run on any kind of ramdisk at all.
Its like pfsense cant load all of itself into the ramdisk after reboot
Again, no ramdisk if not told so! Don't jump to conclusions that you haven't configured.
@abailey10 said in Memory usuage after reboot:
This could be hardware related, except if i get an update and it reboots memory usage will be 18 percent which is normal not 7 percent
Now I'm confused. You told us above that after a reboot it only uses 7%, not 18% and that this is (in your opinion) the point why it runs "flaky" somehow. Now you say it reboots and is 18% not 7%? Huh?
In the end you have to give us much more to "debug" that non-problem if you want to have a conclusion or explanation. But without ANY data at all - that you were told to please post here - there's not much to say other than: it's your isolated case so please show us more details, logs etc. or live with it. Explanations for ups and downs of memory were already given in spades.
-
@JeGr Only time it uses 18 percent memory is when first install with no reboots, or after update. All reboots result in drop in memory to 7 percent. Yes I set up /var /tmp ramdisk also for 250mb each which equals 500mb yet memory usage is still 8 percent. Although /var default 3.4mb on install uses only 5 percent, just increasing the space /var grows to 8 percent of 250mb which is alot more considering no changes made to the install, no packages added, no tweaks, no qos , just default install. So if it set up a ram disk, why dont i see 500mb being used or reserved? And Im looking for help, not a forum that just looks to defend pfsense blindly. I like pfsense but it has issues also.
-
The RAM usage is almost certainly either unrelated or some side effect of whatever is actually causing the latency you're seeing IMO.
However to track down what is using it we need to see what's actually changing so maybe the first 20 lines or so fromtop aSsorted by RES in each condition.Steve
-
@abailey10 said in Memory usuage after reboot:
not a forum that just looks to defend pfsense blindly
It has nothing to do with "defending" blindly. It just isn't an issue as you try to make it one. I don't see a problem with RAM going up and down. You do. And you try to construct a generic pfsense software problem from it besides Netgate staff telling you, it is not.
So if you have a problem with it besides the RAM up/down in your setup and installation - e.g. your point with pfsense being slow/laggy after reboot and not really responsive - then I'd describe and submit logs to that so we can try and help fixing that.
I like pfsense but it has issues also.
No one said otherwise or told you "the product is flawless". If it were, we'd not have patches and updates. But ranting on about a non issue (e.g. RAM) is pretty much useless if all you do is give an opinion about it but NO logs whatsoever so we could actually have a look at it. @Gertjan @stephenw10 and @Derelict already posted multiple hypothesis about the problem with the plea to give us something to work with. Yet all you do is rant on about memory issues instead of showing outputs from top, ps, etc. How about some help?
-
It is possible that this is some entirely new issue and this is first time we are seeing it reported.
However the memory usage or lack of it is only an indication of some change, it's not itself a problem. And it might be a completely unrelated change.
@abailey10 Do you know a specific build that was not affected by this? Can you test the RAM usage in that? Can you test a 2.5 snapshot?
Steve
-
@stephenw10 said in Memory usuage after reboot:
It is possible that this is some entirely new issue and this is first time we are seeing it reported.
Not to be misunderstood: I'm totally for debugging that. But then I'd like to see some actual data, logs and readings instead of accusations and ramblings and textblocks ;) As I said, give us some data to work with :)
