unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs and/or Lisp on Lego Mindstorms?
Date: Wed, 11 Apr 2018 08:45:40 +0200	[thread overview]
Message-ID: <20180411064540.GB6361@tuxteam.de> (raw)
In-Reply-To: <jwvfu42oi7u.fsf-monnier+gmane.emacs.help@gnu.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Apr 10, 2018 at 05:39:11PM -0400, Stefan Monnier wrote:
> >       * Support for stopping motors when the
> >         object is garbage collected
> 
> FWIW, this would be a typical example of ill-advised use of finalizers,
> in my book.

:-)

Ah, old war stories come to mind. Like that old "enterprise" class
application in Java which relied on database connections being
closed whenever its parent object got garbage collected.

The app tended to work (for some value of "work") until management
decided to buy more RAM for the machine. Lots of more RAM. The app
started crashing (about once a day), and since "booting" the whole
thing took around half an hour, users were... hmmm.

Lots of cheerful debugging ensued. The result: since now the machine
had much more RAM, it didn't run into memory pressure that quickly,
meaning it hadn't to garbage collect as often, meaning it could
leave more stale DB connections lingering around meaning... the
application ran into the maximum licensed DB connections (did I
mention it was an Oracle DB, where you pay for everything)?

So yes, Stefan's short phrase above is worth careful consideration :)

Cheers
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlrNrxQACgkQBcgs9XrR2kYZlACeLvon/aFkO69JrHfmVriLXtsI
jvIAn1EMeMWtlPzXh1uz7RRX+w2C78my
=dDnj
-----END PGP SIGNATURE-----



  reply	other threads:[~2018-04-11  6:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02  0:51 Emacs and/or Lisp on Lego Mindstorms? Emanuel Berg
2018-04-05 10:31 ` Marcin Borkowski
     [not found] ` <mailman.11730.1522924324.27995.help-gnu-emacs@gnu.org>
2018-04-06 18:50   ` Emanuel Berg
2018-04-08  6:06     ` Emanuel Berg
2018-04-09 19:52     ` Marcin Borkowski
     [not found]     ` <mailman.11945.1523303599.27995.help-gnu-emacs@gnu.org>
2018-04-09 21:02       ` Emanuel Berg
2018-04-10  4:27         ` Marcin Borkowski
2018-04-10  7:40         ` tomas
2018-04-10 21:06           ` Stefan Monnier
     [not found]           ` <mailman.11985.1523394413.27995.help-gnu-emacs@gnu.org>
2018-04-10 21:26             ` Emanuel Berg
2018-04-10 21:39               ` Stefan Monnier
2018-04-11  6:45                 ` tomas [this message]
     [not found]         ` <mailman.11961.1523346023.27995.help-gnu-emacs@gnu.org>
     [not found]           ` <86y3huaokd.fsf@zoho.com>
2018-04-10 19:55             ` tomas

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180411064540.GB6361@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).