Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
For any model 2800, 100 Mbps may drive the 2800's CPU to 100%. If that is happening, all users are likely to see poor performance when it does.
If this is only caused by users download large files from the main branch, policing or shaping on the main branch side, to restrict how much traffic can be pulled down from the main branch may mitigate the issue.
Additionally, if you shape, you may want to use other than FIFO queuing when shaping. If you police, ideally want to target the bandwidth "hogs", but that can be difficult depending on your main branch's QoS features. (You may be able to target select traffic types that traditionally may draw much bandwidth.)
