Sravya, can you give us some details on what you are using to trigger your cache? When misconfigured it will definitely cause a Cache miss. I used code similar to Holger's above (though not the same) on a test proxy, here was the result:
You can see the first result took 5.29 seconds due to its large size, while the second request, a successful cache hit, only took 183ms.