I just thought this basic info a bit relevant as the answers so far are focusing on time based measurements from within a vSphere virtual machine, where this is in some cases a crucial circumstance for correct analysis.
It also of course relates directly to the theme of this particular unfinished answer and its comments. It may be of use to someone. Naturally it is all googleable too. When there are a ton of apps, connections, services running on one host the system doesn't know that everyone needs to play nice together.
Windows Server naturally tries to use all of it's resources to complete everything all the time unless it is made aware By implementing WSRM you can set resource limits by all sorts of variations to make sure there is an even playing field for everything running or users connected. You will have to test WSRM to find a happy medium of balancing resources among everything but also not affecting performance levels everyone has grown accustomed to.
Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 7 years, 11 months ago. Active 5 years, 11 months ago. Viewed 47k times. However, at certain points during the week and now, almost daily , new user logons produce the following errors: Event ID Windows cannot log you on because your profile cannot be loaded.
I'd like to know: What resource s is this error message referring to? What's actually constrained? Is there an OS-level tunable or configuration that can help with this? Users are content with performance, except for the increased frequency of this error message.
Is there something else at play here? Is there an absolute limit to the number of users a terminal server can accommodate? Improve this question. Is this your problem? I can't say that I've experienced this on a Windows Server R2 Server, but I ran into it a lot on and , so maybe it still applies.
Most of my research has led me to solutions geared towards Windows environments, but maybe my Google skills are off now This is for , but you may want to look at if it seems relevant: support. ErikE Those registry entries are ignored in R2.
Show 1 more comment. Active Oldest Votes. This has been solved. Improve this answer. Community Bot 1. Sometimes clients will have terrible print drivers that get copied up to whatever servers they RDP too. There could also be an issue with the customer installing local printers on the TS instead of the GPO--distributed printers I vaguely recall this issue happening to me once, but then an unrelated total corruption happened, so I just reinstalled everything.
I'll certainly bookmark this in my Evernote, if I experienced a similar problem in the future. Again, thanks! Add a comment. But in Linux Before complaining about processes being high versus Linux, add the "threads" column to process monitor and see how many of them you see Comparing them is unfair to both kernel designs. MikeyB MikeyB Can I just add more vCPUs? Also, it's not likely directly the source of your login failures.
Which I'm trying to get to the bottom of Might be worth throwing up some perfmon counters to check if that's what's happening to you. From the technet blog titled RDS Sizing and Capacity Planning Guidance : We always felt the need of Hardware capacity guidance and sizing information for Terminal Services or Remote Desktop services for Server R2, Whenever I am engaged in any architectural guidance discussion for RDS deployment i always get a question what needs to be taken into consideration while deciding the hardware configuration and to do capacity planning.
More applications used i. Office, CAD Apps and etc. Network should not have more than 5 hops, and latency should be under ms. HopelessN00b HopelessN00b 53k 31 31 gold badges silver badges bronze badges. I have very little time so I'll just do a sketchy answer and hopefully flesh it out later. ErikE ErikE 4, 1 1 gold badge 18 18 silver badges 25 25 bronze badges. Are you suggesting that I need to reduce context-switching?
The figures reported via procmon were far lower than other examples I saw online. I'm suggesting you look at if it may be relevant to your issue. If you have measured it and the amount seems low according to your research it obviously is not. What is the issue you are facing? In that case you may want to change the isolation level to Read committed Snapshot. Please be aware that, there are other issues like temp db usage when we change isolation level.
But Googling, I see that back in SQL days people were saying 8, to 10, per second were getting to be too high. Only servers back then typically had just two or four cores, ran way slower than today. How many SPIDs does your server run, and how many cores does it have? Maybe 20, per second is very low today, for a big app on a big server!
I see someone else, a couple of years ago, worrying about , per second! Any CPU spikes? I agree with Vijay Do you see high processor queue lengths in case you have captured this in any of your perfmon snapshots. In case of OLTP where various small queries run very often you might see frequent context switches..
Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Sign in to vote.
0コメント