Hi Nishchay,
The queue delay time is the amount of time in milliseconds that the ACE waits before emptying the queued data for encryption.
queue-delay timeout milliseconds
The ACE queues packet data from the server before encrypting it for transmission to the client. The ACE empties the data from the queue for encryption when one of the following events occurs:
• The queue reaches 4096 bytes.
• The server sends a TCP-FIN segment.
• The queue delay time on the ACE has passed even though the queue had not reached 4096 bytes.
The queue delay time is the amount of time that the ACE waits before emptying the queued data for encryption. By default, the queue delay timer is disabled. You can set the delay time by using the queue-delay timeout command in parameter map SSL configuration mode. A value of 0 disables the delay timer, causing the ACE to encrypt data from the server as it arrives and then send the encrypted data to the client. The queue delay applies only to encrypted data that the ACE sends to the client.
I found this option is recommended only to preserve ssl resources on the ACE and its suggested to have 200 – 300 milliseconds of the timeout value so instead of encrypting and sending more smaller blocks of data, we would compact several blocks of data that we receive from the server during this delay and encrypt it to send it to the client. I could not find anything where its suggested to keep it with a very low value of 1 millisecond to improve the performance. Lets say the ACE sends data received from the server every millisecond to be encrypted to send to the client, the time taken to encrypt the data to send it to client will be more as many small packets would need to be encrypted and might cause delay.
Hence I would request you to try removing this command and see if it helps.
Thanks,
Rajesh.
