From: "James E. King, III" <jking@ariessys.com>
To: linux-mm@kvack.org
Subject: Hello
Date: Wed, 28 Apr 1999 11:28:07 -0400 [thread overview]
Message-ID: <v04020a01b34cd7f3c7c3@[198.115.92.60]> (raw)
I'm not much of a kernel type, but I do have some formal background on OS
working and reading through the Linux-MM site brought back lots of stuff.
Anyway, I am working on a project where we have a large database split into
12 segments, and I want to put some of the indices in those segments into
memory. The indices for all of the segments takes up about 4 GB.
The database server is a multi-threaded proprietary one that I ported over
to Linux - it already runs on MacOS (yes, true!), NT, Solaris, AIX.
I have a couple of questions (assume I am talking about the latest versions
of any component, like kernel or lilo or ramdisk):
1. If I purchase a Quad Xeon 550 with 4 GB of memory, will Linux work on it?
(I saw the whole thing about tweaking kernel parameters to change from a 3:1
split to a 2:2 split)
Should I just buy 2GB - will I be able to use the extra 2GB?
2. Can I create a large (let's say 1GB) ramdisk or memory filesystem?
Obviously the more index I can fit into memory, the faster the result.
I'd really, really like to use Linux here. It has proven itself as our
mail/DNS server and hasn't crashed once in over 2 years, where we reboot NT
servers weekly.
I am willing to do some kernel hacking and experimentation. I have not
been able to find another resource related to large amounts of memory with
Linux. Hopefully through my experiences I will be able to produce a Linux
VLM-HOWTO!
Thanks.
_/ _/_/ _/_/_/ _/_/ _/_/ James E. King, III
_/_/ _/ _/ _/ _/ _/ Aries Systems Corporation
_/_/_/ _/_/ _/ _/_/ _/_/ 200 Sutton Street
_/ _/ _/ _/ _/ _/ _/ North Andover, MA. 01845
_/ _/ _/ _/ _/_/_/ _/_/ _/_/ (978) 975-7570
(978) 975-3811 FAX
<http://www.kfinder.com/>
Enhancing the Power of Knowledge(r) jking@ariessys.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-04-28 15:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 15:28 James E. King, III [this message]
1999-04-29 14:27 ` Hello Benjamin C.R. LaHaise
1999-04-30 0:54 ` Hello Stephen C. Tweedie
1999-04-30 14:20 ` Hello Manfred Spraul
1999-04-30 16:12 Hello Manfred Spraul
1999-04-29 16:20 ` Hello Benjamin C.R. LaHaise
1999-04-30 0:55 ` Hello Stephen C. Tweedie
1997-01-01 15:29 ` Hello ak
1999-05-04 11:45 ` Hello Stephen C. Tweedie
1999-05-01 13:56 Hello Manfred Spraul
1999-05-04 11:44 ` Hello Stephen C. Tweedie
1999-05-01 14:00 Hello Manfred Spraul, ak
1999-05-04 11:41 ` Hello Stephen C. Tweedie
1999-05-01 15:25 Hello Manfred Spraul
1999-05-05 15:27 Hello Manfred Spraul, Stephen C. Tweedie
1999-05-04 23:20 ` Hello Stephen C. Tweedie
2001-09-04 11:53 Hello Brian Elias
2012-07-13 15:16 hello Olivia Gilmore
2012-07-17 4:06 hello Brad Mcneill
2012-07-23 12:45 hello Victoria Metz
2012-07-25 13:29 Hello Eliza Burke
2012-07-25 20:38 Hello Melissa Culver
2012-07-28 9:01 hello Romeo Grimes
2012-07-31 4:56 Hello Erick Andrade
2012-07-31 17:06 Hello Lee Montoya
2012-08-02 12:06 hello Orlando Villegas
2012-10-14 5:22 Hello Quincy Thompson
2012-10-16 0:16 Hello Freeman Xiong
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='v04020a01b34cd7f3c7c3@[198.115.92.60]' \
--to=jking@ariessys.com \
--cc=linux-mm@kvack.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