From: <tomas@tuxteam.de>
To: guile-devel@gnu.org
Subject: Re: patch for mmap and friends
Date: Sat, 14 Jan 2023 17:41:16 +0100 [thread overview]
Message-ID: <Y8LbLPrBE6oUy7iu@tuxteam.de> (raw)
In-Reply-To: <445d3567-9bbf-487b-f338-8a16903e9e62@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
On Sat, Jan 14, 2023 at 04:18:58PM +0100, Maxime Devos wrote:
[...]
> (While it is recommended for Scheme code to keep a reference to the port to
> manually close afterwards, to free resources faster than waiting for GC, it
> is not actually required.)
Oh, oh. I've got a little anecdote to share here. The context was a Java
application, running on Sun medium-sized iron. It was slow & clumsy and
the customer decided to double the machine's RAM (these were times where
200 MB were quite a thing).
The application crashed a couple of times a day. Some log file poking
later it became clear: at the other side there was an Oracle database
and the app was exhausting the (limited) max number of connections
allowed for the license they had. More RAM -> less GC and the app was
relying on the object destructors to dispose of the unneeded database
connections.
There I learnt one shouldn't ever use memory as proxy for other
resources :-)
(The end of the story was that we could convince the user to have an
application under a free license and a free database :)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2023-01-14 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 0:49 patch for mmap and friends Matt Wette
2023-01-14 1:00 ` Matt Wette
2023-01-14 15:18 ` Maxime Devos
2023-01-14 16:31 ` Matt Wette
2023-01-14 22:08 ` Matt Wette
2023-01-14 22:42 ` Maxime Devos
2023-01-14 23:46 ` Matt Wette
2023-01-14 16:41 ` tomas [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y8LbLPrBE6oUy7iu@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-devel@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).