It's easy to create and consume RSS with ASP.NET. This is usefull to transport documents without the overhead eg of SOAP. The only problem is that if the implementation is bad ~ 99% increased traffic will be generated.
Consumer can pull the rss frequently and the whole amount of data is transfered again and again.
RSS must have at least two optimizations:
1) Conditional GET
Means that the RSS Data is signed by a value called ETAG. The server transfer this to the client and the client send it back during request. The server send back a HTTP 304 status code if the etag is identical. No rss data is transfered again.
2) HTTP compression
XML is a very overheaded format and can be compressed very effectiv.
With a usal RSS reader or if include a 3rd party RSS in your website you can not see the quality of the rss source. HTTP Fiddler can help to detect that kind of issues.
For easy testing your feed i have implemented a test page.
Try it and give feedback.
I have not made performance test or crash test, but included GZIP decoding.