-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RAM consumption is too damn high #24
Comments
@alexAubin, what kind of platform you are using? Would you please show the result of |
Looking at a Sympa server with a few mailing lists, the processes eating most of the RAM are the task manager and WWSympa ( both a bit over 500M virtual and 200M residential memory). |
Hi there. I've been working in a debian 8 VM, where I had no memory issue (probably because nothing installed beside Yunohost and Sympa), and then in a debian 8 VPS, a Digital Ocean droplet with 512 Mo of RAM, where I started encountering the issues. Here's the result of
Cheers ! |
Thanks for information. Now I understand you are using Debian 8 amd64. FYI, below are a few example of machines I maintain (it takes short after startup). Is there any remarkable difference from your environment?
|
Edit: btw I'm running Sympa 6.2.16 Hi ikedas, the main difference I see is that I'm running Linux 3.x :
The return of Here's the return of the
And additionally, the output of
And the status of RAM (among which 500MB of swap) :
|
I guess using i386 packages can solve (at least mitigate) problem on memory usage. IMO 64-bit architecture (8 bytes for integers and pointers) is no more than space-wasting for many applications including Sympa. |
Stagnated issue. Closed. |
RAM consumption is still too damn high. and this should be adressed some day |
Marc, can you show the evidence?
2017/12/24 2:29、Marc Chantreux <notifications@github.com>のメール:
… RAM consumption is still too damn high. and this should be adressed some day
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No updates. Closed. |
Hello, I'm sorry to say that Sympa is still, in late 2021, using gigantic amount of RAM, for no valid reason. I only have a screen capture of this, but it's quite interesting. https://www.patpro.net/cafesale/symparam.png I'm running sympa-6.2.62 + perl5-5.32.1_1 on FreeBSD 12.x-RELEASE (amd64) After a restart of Sympa, I've this:
|
As far as I can tell, this is actually a problem with FreeBSD 12: If you think this actually not the case, please open a new issue. |
looks really promising, thanks for the pointer! |
When packaging Sympa for Yunohost, I soon realized that sympa (and even cpan, during install !?) was getting killed because of OOM. After investigating, I saw that Sympa, when not doing anything (i.e. right after install) consumes about O(400 Mo) of RAM.
I understand that Sympa is meant to be an entreprise-grade/large-scale application, but imho this is way too much. In the Yunohost community (but probably in the self-hosting community as a whole), people have heard of Sympa and expect it to be a good program to manage a few list for their friends or local club, i.e. basically not more than a dozen of list with O(10~100 people) on it.
But because it takes O(400 Mo) of RAM, the cost of running it is pretty high. ARM board used for self-hosing typically have around 512 or 1 Go of RAM. So basically, running Sympa costs half a Raspberry Pi. In terms of VPS, such as Digital Ocean droplets, 512 Mo of RAM costs approximately 5$ / month, so running Sympa on a VPS costs about 5$ / month.
And this is for a program that is idling 99% of the time. Right now, in the context of Yunohost packaging, I simply added 500 Mo of swap to the system at the install, but I expect this to drastically reduce the life of SD card for people running ARM boards.
Isn't there any way to reduce the RAM consumption to some acceptable level (e.g. O(50 Mo)) ?
The text was updated successfully, but these errors were encountered: