I ran into "customer feelings" a couple of times. Usually this ends up with understanding an application and finally learning something about (bad) application programming.
The first thing I would do in your case is to figure out where the customer "feelings" about slowness come from.
What is slow?
F.e. running a database application with thousands of small packets for a request across the internet can not be cured by any "magic box". It is just round trip time multiplied with number of packets to Ack. And as long as "Scotty or Spock do not reveal the Warp thing" we will be limited by speed of light.
You can of course increase your throughput, but this will only help in case the PIX is running at maximum speed for some time already.
What is your interface load on the PIX/internet connection? In case they are below 50% an upgrade of internet access speed will not change anything. It´s a waste instead!
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...