when the throttling happens, do you see any errors/warning in the deployer logs? It would be interesting to understand the exact reason for the throttling. In principle, I think that the windowSize and Workers that you currently have is already too high, so increasing these will not avoid the throttling status and will probably introduce other behaviors (like locks on the broker database due to the high number of workers writing at the same time into the database).
As mentioned on the previous post, it may help to clean up some folders. In addition to clean up the temp folder that the Publisher uses (by default, c:\temp > as defined in the Snap-in under Publisher settings) as well as the transactions folder that the Transport Service. Although i dont think these actions will really impact much the throttling - it is always good to do some cleanup of these folders.
Probably, the threads configured in the Publisher side are quite high, so the transport is sending a lot of load at the same time to the deployer. So, can you share the number of threads for rendering and deploying on the Snap-in, as well as, the number of cores on the Publisher server.
Moreover, throttling might happen because the deployer needs longer to write content: large packages to deploy and/or no database maintenance tasks on the broker.
