I don't think I'd want to view the state of my chunking after a night of heavy driving... Seriously though, I found this post that describes how to take your massive viewstate and break it up into smaller chunks to make certain firewalls happy.  I gotta think that's the least of your problems though if you have a viewstate that's that huge.  There are many controls that you can set enableviewstate=false on, and you should always be careful trying to store the entire contents of a databound control like a repeater or gridview.  ASP.NET does introduce a lot of bloat on the HTML side, but there are things you can do to get a lean page.  Keep the names of your controls as short as possible, especially when there's nesting involved, and look into compression of your output, such as with GZIP with a plugin for your particular web server software