Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. What resource metrics would you look at to make an assumption on whether or not a server was idle? A machine is idle when it's not performing the task it's supposed to perform for lack of requests. For example, if you had an email server, you could determine if it was fielding any requests from the email application on it.
If it isn't, and that's the only thing on there, then it's idle. Things of course get more complicated with collocated services on a single node. Linux and Windows both have logon auditing. Windows has the performance monitor for monitoring general network activity, and many built in counters of active sessions for various services.
I don't think any of the metrics you've listed are really good indicators of activity or inactivity since there are so many ways to get 'false positives', depending on what you're looking for.
The best approach is to collect daily metrics from all your production instances and compare the numbers. You may have some workloads that you can distribute across your server farm more evenly thus, giving you a overall lower load average. You want all your servers to be operating in the sweet spot of not to high, yet not too low thus to maximize your overall perforamnce.
There is no meaningful way to classify a server as idle without context. Sign up to join this community. A reason for doing so has been increasing playtime and thus overall chance of earning unlockable items, such as weapons or cosmetic items , through the item drop system. The term idling stems from the idea that the player's character remains virtually immobile during the game, as they wait for the system to deliver items. The community also describes someone who is idling as AFK Away from keyboard.
However, these terms also refer to any player not moving or moving but not playing to game objectives for any reason. Valve's changes to the item drop system in April reduced the effectiveness of idling as a means of obtaining drops through the introduction of a "weekly item cap". Idling for drop is now considered obsolete due to a patch that nullified this system, which requires the player to confirm their previous drop in order to be eligible for more. Moreover, Casual Mode servers and many Community servers now automatically kick "for being idle" players that are not moving for some time.
On the other hand, certain Idling Servers exist that defeat the need for idling players to confirm each drop.
The early versions of the item drop system was seen by many as unfair, with many arguing that the amount of hours played needed to receive items was not favorable to all. Players sought ways to boost their hours through several means. The earliest method involved simply launching the game, joining a server , and minimizing the game to the background; the player remained idle in the server, increasing their total playtime and increasing their amount of dropped items.
The inconvenience of running the game in the background persistently in order to earn items lead to the creation of third-party programs. Intended originally as a method of research into the item drop system, the program quickly gained popularity, providing statistics and notifications to users upon receiving an item.
As idling previously required the user to load the game and run in the background, SteamStats appealed to many players as an ideal way to earn items efficiently, without the need to play for large amounts of hours or to place a drain on system resources and power. On the September 2, , blog post, Valve took a zero-tolerance stance against the use of external applications to manipulate the item system, removing all items earned through these applications to date.
By using the DCIM you can easily identify where you have an idle server. An Intelligent PDU can help you to monitor your previously idle servers. According to a recent Stanford University study, one out of three servers might be hung or idle in your data center at any given point. Together, a DCIM and Intelligent PDU can give you the real-time insights that you need to more efficiently identify idle servers, adjust power consumption needs, power off idle servers, and create an optimized IT environment.
With services such as the Cisco Application Dependency Mapping Service which I blogged on here back in May , and the advanced network, server and application discovery technologies we use as part of this service, our consultants can take the weight off you. Contact me on Twitter if you need to start saving! Tags: applications Cisco Services CiscoUCS data center data center facilities energy efficiency IT transformation server virtualization Servers software asset management software licensing.
One Comment Thanks Stephen for your insight.
0コメント