× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



1.2 GB sounds right based on what you see, Sorry what do you mean, how
does that play with some of the figures in show stat?

Now that you know the "cost" of an average session 1.5 MB, (which by the
way is about average for a mail server), you could look at REAL workload.

while you have 400 users defined, if you look at Server.Users.Active30Min
that give you a better idea of "real" memory requirements.

Lets assume that with 400 users the Server.Users.Active30Min = 300, then
1.5 times x 2 times 300 gets 900 Mb of memory to support this server.



Walter Scanlan
Senior Software Engineer
Office: 1 720 342 5837
Cell: 507-990-4539




From: rob@xxxxxxxxx
To: Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>,
Date: 07/25/2011 08:48 AM
Subject: Re: Memory usage for Domino
Sent by: domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx



Ok. That helps. That median file was 2.9MB for ($Inbox). I picked 10
files, including that one. The size of that view ranged from 148,864 to
3,754,048 with the average being 1,540,978. Some people are really
religious in moving stuff out of inbox into other views - others aren't.
Me? I have over 1,500 unread messages in my inbox let alone all the stuff

I've read.

So if I take 1.5MB x 2 x 400Users I get 1.2GB. That's easier to swallow
than 10.4GB.

How does that play with some of the figures from show stat, etc?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.