This week, we:

• got 11,040 messages from 245 different IP addresses.
• handled 20,069 sessions from 1,915 different IP addresses.
• received 344,743 connections from at least 97,338 different IPaddresses.
• hit a highwater of 42 connections being checked at once.

Connection volume is down from last week .This week the volume peak was clearly on Monday instead of Wednesday:

Our current connection to the campus backbone is a 100 megabitconnection. While we have a (somewhat) new gigabit backboneconnection, we are not using it yet because we need to revise ournetwork architecture.

One of the issues with our current network setup is that it wasdesigned before firewalls were common. As a result, our currentbackbone connection connects directly to one of our /24 subnets, where(of course) a number of our servers live. This forces us to use abridging firewall

A comment on the previous entry got meinterested in what exactly cost all the time when using Python longs asbitmaps.Some poking shows that the time & takes scales up based on the smallerlong involved, and the time | takes scales based on the larger longinvolved. While this is not particularly surprising, it means thatsetting and clearing any bit has a cost based on how big the bitmap is,ie, what the largest set bit is.

(Checking low bits in a large bitmap is relatively cheap,