> I am guessing most GlowMucks are small to mid-size mucks.

I'd concur. Most mucks (muds, even) tend toward small. To give some
ball-park ideas:

MUCK University has about 2000 database items, with low activity.
* Its using about 10mb of memory.
* The actual game occupies about 15mb of disk space
* I keep 10 (11, really) rolling backups of the actual database file, which
is
around 5mb each for an additional 50mb which illustrates that it depends
on the
backups you keep.
* ps -ux reports that it is using 0% of the proccessor (a p-233) which means
the
usage is too small for ps to report.
* I have another process on the same machine that uses 50% of the processor
and
technically 100% of the physical memory...and University doesn't notice.

Now we can compare to Narnia, which has around 27,000 database items (many
of which have extensive string data with them), typically 10-25 players
depending on time of day, has many active programs (they have programs that
move 'zombie/puppets' around, food that decays, etc.):

* Its using about 30mb of memory
* The game occupies about 163mb (includes 37mb in logs...eesh)
* They keep 12 rolling backups of the 20mb database file (280mb)
* Uses around 1% of the CPU on the machine it is on (Pentium 4 3Ghz)

---
A new world I'd expect could run on a pretty minimal account or machine. An
older world with good player flow with lots of string data will need more
memory, disk, and processor, but getting to that point takes a fair bit of
time...

Strictly speaking, you should be able to run a small Glowmuck server on a
486 doing nothing else, that has around 16mb memory, and some old disk
drive, depending on how many backups you want to keep. Maybe even more
minimal. I no longer have anything slower than a p-60, so I wouldn't know.
:)

f.