From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: OT - RAM disks - WAS Re: [gentoo-user] Network failed and weird error message
Date: Mon, 14 Oct 2013 07:03:51 -0400 [thread overview]
Message-ID: <525BCF97.3020204@libertytrek.org> (raw)
In-Reply-To: <525B1575.3070209@gmail.com>
On 2013-10-13 5:49 PM, Dale <rdalek1967@gmail.com> wrote:
> Talk about putting some stuff on tmpfs. O_O I have always wanted to
> copy the tree to tmpfs and run "time emerge -uvaDN world". Just to see
> how fast it will go. lol
I remember once I worked for an Apple reseller that had this accounting
program that required them to do some kind of 'reconciliation' every
month that required a massive amount of processing - it took like 36
hours or something ridiculous (literally almost took all weekend), and
he had implemented a rule that someone had to be there the entire time
to baby sit the process - apparently it wasn't uncommon for there to be
an error that would require them to restart it - and this was on a
pretty powerful system at the time.
Well, one weekend, when we were building a system for a customer with
tons of RAM (for the time) I talked them into a little experiment. The
boss didn't believe me when I told him I could get the reconciliation
processing time down to less than a day (I told him probably just a few
hours, but wasn't sure)... so we made a bet.
I took a Quadra 900 (or maybe it was a 950), and added a bunch of RAM -
I think we got it up to 128MB or something ridiculous (this was in about
1992). The accounting DB was about 40MB at the time, but hey, we had the
RAM, so I just loaded it up.
I created a RAM disk, copied the entire Accounting DB into it, and
started running the reconciliation. The process finished after about 45
minutes (I was even surprised at that), and while there were no errors
and it said it had completed successfully, the boss was sure that
something had gone wrong. So, he re-ran it the old way on the old
server, and almost 2 days later, when the numbers matched, he just shook
his head and paid me off, muttering about the lost weekends over the
last 5 years he'd been there. He kept that machine around for running
the reconciliation for at least a few months, but then I left, so no
idea how long he kept it for...
next prev parent reply other threads:[~2013-10-14 11:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 16:09 [gentoo-user] Network failed and weird error message Dale
2013-10-04 19:35 ` Alan McKinnon
2013-10-04 20:19 ` Dale
2013-10-05 8:54 ` Alan McKinnon
2013-10-05 10:06 ` Dale
2013-10-05 13:41 ` Bruce Hill
2013-10-06 18:36 ` Dale
2013-10-06 18:55 ` Alan McKinnon
2013-10-06 19:24 ` Dale
2013-10-06 19:52 ` Dale
2013-10-06 19:59 ` Neil Bothwick
2013-10-06 20:31 ` Dale
2013-10-06 20:55 ` Frank Steinmetzger
2013-10-07 0:11 ` Dale
2013-10-07 8:08 ` Neil Bothwick
2013-10-06 21:07 ` Alan McKinnon
2013-10-06 22:39 ` Neil Bothwick
2013-10-07 0:36 ` Dale
2013-10-06 21:42 ` Bruce Hill
2013-10-07 0:28 ` Dale
2013-10-07 8:06 ` Neil Bothwick
2013-10-07 14:17 ` Dale
2013-10-04 21:52 ` Walter Dnes
2013-10-05 9:04 ` Alan McKinnon
2013-10-05 10:13 ` Dale
2013-10-05 13:37 ` Alan McKinnon
2013-10-06 18:38 ` Dale
2013-10-13 12:26 ` Dale
2013-10-13 17:31 ` Mick
2013-10-13 21:49 ` Dale
2013-10-14 7:23 ` Mick
2013-10-14 15:18 ` Dale
2013-10-14 11:03 ` Tanstaafl [this message]
2013-10-14 12:08 ` OT - RAM disks - WAS " Dale
2013-10-15 5:53 ` Pandu Poluan
2013-10-07 2:29 ` Dale
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=525BCF97.3020204@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.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