We've been experiencing issues with Citrix-hosted applications freezing, even when server performance metrics appear normal. After investigating, it seems that some heavy users are rapidly clicking—especially hammering Enter or F5—which leads to short CPU spikes on the local Citrix client and results in session problems. Has anyone else seen similar trends? Do you handle this issue on the server side or the client side? Has anyone tried implementing local input-throttling or client-based input dampening? I've been working on a client-side method that smooths out these input bursts, which has really helped with troubleshooting. I'd love to hear what solutions or strategies others have tried!
2 Answers
I haven't worked directly with Citrix, but for remote UI deliveries, I've implemented rate limiting for user inputs. In my experience, Unix makes it easier to apply these controls compared to Windows. If memory serves, the TCP port for the UI might be separate from the actual delivery to the user, but it's been a while since I dealt with that. Just my two cents!
Haha, I think your approach is interesting! I can relate to the hassle of keeping users from overloading the system. While I was joking earlier about the concrete and hole strategy, finding a way to manage user input effectively is serious business. Have you considered a balance between client and server-side adjustments?
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures