From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: musl new-year's infrastructure resolutions
Date: Mon, 2 Jan 2017 16:59:49 -0600 [thread overview]
Message-ID: <586ADB65.7020200@adelielinux.org> (raw)
In-Reply-To: <20170102200620.GB89009@wopr>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 02/01/17 14:06, Kurt H Maier wrote:
> On Mon, Jan 02, 2017 at 02:16:24PM -0500, Rich Felker wrote:
>> Mantis doesn't seem so bad as a user but I have no idea how bad
>> it is under the hood. Redmine looks kinda nice and Alpine uses
>> it.
>
> Redmine is a very typical Ruby on Rails application. It works as
> advertised but requires familiarity with that ecosystem to install
> and operate. Mantis is a php application with all of the typical
> travails of php.
That's a very diplomatic assessment of Rails.
I administer multiple Rails applications - GitLab, a custom CMS, one
of the eCommerce packages, and a full Web application that was
developed in house. I cannot believe how much of a resource drain
they are, even having gone through the pain of optimising the entire
stack. I think the smallest RAM footprint I've ever seen out of Rails
is 450 MB resident.
This isn't even a Ruby problem; I have seen Sinatra using under 50 MB.
For a large Redmine install with a lot of users and some concurrency
(i.e. multiple people doing /something/ at the same time), I wouldn't
use a box with less than 2 GB RAM and dual-core. And that's pushing it.
Look, I used to *be* a Rails developer. I like the rapid prototyping
that it allows and I even *still* use it for that. But it isn't
something I would ever choose to run in production.
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJYattiAAoJEMspy1GSK50UIMIP/RKQN5hiA+cigy7eZwMY3YEx
+eps9jp0uBSR4LuHRtKf06HhTgsfwTuy+/NRE2rdykSU2lXhh+QoedsclQ1Ga1Zr
/gXGDMBjPvhkH8QDzxO0Um8DuIm/sDuz2ByysxFBX6k4/Hhqc+esodM+j6adyY1g
Zsx8lJWXW1DXu2J1/Tp/uAKUpdRY6Xdygq76z9zfzgH6uJ3ia0pb7lcYn+Sgzsdb
rnAf1jr/BqrDrSsEKbcNSB2SLW26k868GhsY7bKAF3FY2q4CAHatnc2bfM/qBWz8
8IOGjzUqk3mI+6JJgFq+uIbeXrc0Jpa+J7igEwOEYaHmNgjfaCciWt558/XjfnmM
ndu8KkO5TaRz584olVpWbzkF0+YgDsygIOJx19GS7I5Okg/B9Xs5t/7+rTetshs/
qZvU8P+wiIeTi69c75ByrnZRwICoX1KL6I9dAfOJtjPT51Xb29X8MXmN48moZBYG
5oXxaaafqU9D7nRAArzgphZarJR7eVSfA7MbH49539kR4+wHJIXvC2cYd5IgfiSt
Wm9T/D1OkO0MaXco0YXRfM6bVJh4uWU89FggPj2yqWStL/GNH5fxDUp8ntzvdy7w
aw58+ObcSOJpVgpm/pfRJJGk2Jrz+SmoTC6PFEIM3KFu3Ak1wNehoDllsEIfrTA/
/1J2PsOAxZq05VidsD5E
=98Mf
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-01-02 22:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 23:37 Rich Felker
2017-01-01 22:37 ` A. Wilcox
2017-01-02 2:31 ` Rich Felker
2017-01-02 2:33 ` Rich Felker
2017-01-02 5:32 ` A. Wilcox
2017-01-02 5:40 ` Rich Felker
2017-01-02 6:39 ` Khem Raj
2017-01-02 16:58 ` Rich Felker
2017-01-02 18:11 ` Alexander Monakov
2017-01-02 18:23 ` Rich Felker
2017-01-02 18:15 ` Solar Designer
2017-01-02 18:25 ` Rich Felker
2017-01-02 18:27 ` Kurt H Maier
2017-01-02 18:36 ` Rich Felker
2017-01-02 18:52 ` Kurt H Maier
2017-01-02 19:16 ` Rich Felker
2017-01-02 20:06 ` Kurt H Maier
2017-01-02 22:59 ` A. Wilcox [this message]
2017-01-02 23:09 ` Kurt H Maier
2017-01-02 19:10 ` Matias A. Fonzo
2017-01-02 19:18 ` Rich Felker
2017-01-02 19:28 ` Matias A. Fonzo
2017-01-03 1:20 ` Laurent Bercot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=586ADB65.7020200@adelielinux.org \
--to=awilfox@adelielinux.org \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).