nanog mailing list archives
Re: AWS Elastic IP architecture
From: Christopher Morrow <morrowc.lists () gmail com>
Date: Thu, 28 May 2015 14:54:08 -0400
On Thu, May 28, 2015 at 2:39 PM, Michael Helmeste <elf () ubertel net> wrote:
and spending a few gigabytes of RAM for every /23
it's not clear to me that you need ram at all for this... there are multiple dimensions to the scaling problem I was aiming at, this is but one of them. anyway, unless an EC2/aws/etc person speaks up I bet we can 'conjecturebate'(tm) forever without success.
Current thread:
- AWS Elastic IP architecture Luan Nguyen (May 28)
- Re: AWS Elastic IP architecture Ca By (May 28)
- Re: AWS Elastic IP architecture Christopher Morrow (May 28)
- RE: AWS Elastic IP architecture Michael Helmeste (May 28)
- Re: AWS Elastic IP architecture Christopher Morrow (May 28)
- RE: AWS Elastic IP architecture Michael Helmeste (May 28)
- Re: AWS Elastic IP architecture Christopher Morrow (May 28)
- Re: AWS Elastic IP architecture Owen DeLong (May 29)
- Re: AWS Elastic IP architecture Christopher Morrow (May 29)
- Re: AWS Elastic IP architecture Owen DeLong (May 30)
- Re: AWS Elastic IP architecture Christopher Morrow (May 28)
- Re: AWS Elastic IP architecture Ca By (May 28)
- Message not available
- Re: AWS Elastic IP architecture Christopher Morrow (May 28)
- Re: AWS Elastic IP architecture Blair Trosper (May 28)
- Re: AWS Elastic IP architecture Christopher Morrow (May 29)
- Re: AWS Elastic IP architecture Owen DeLong (May 29)
- Re: AWS Elastic IP architecture Christopher Morrow (May 29)
- Re: AWS Elastic IP architecture Owen DeLong (May 29)