capacity planning for INN

bill davidsen davidsen at
Wed Jun 20 19:26:38 UTC 2001

In article <20010619212824.44596.qmail at>,
Tyrone  <hhssss at> wrote:
| 1. Daily storage for daily full feed (300GB?)
| 2. Memory requirement for INN server (128MB?)

Transit servers 1GB, reader machines 2GB. If the history hash doesn't
fit in memory expire takes forever, so innd+innfeed+expire+histiry.hash
is a place to start.

| 3. Memory requirement for each newsfeed (32MB?)
| 4. Memory footprint per news connection (300KB?)
| 5. Number of concurrent news connection for ISPs (250?)

  Readers or feed? In either case, sounds low. Feeds, particularly from
Typhoon or Cyclone seem to want lots of sockets open. Of course INN has
that polling loop, so this is not the most desirable way to go, but
there it is.

bill davidsen <davidsen at>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

More information about the inn-workers mailing list