Software for Utilizing Idle Workstations on Network – Managing your servers can streamline the performance of your team by allowing them to complete complex tasks faster. Plus, it can enable them to detect problems early on before they get out of hand and compromise your business. As a result, the risk of experiencing operational setbacks is drastically lower.
But the only way to make the most of your server management is to perform it correctly. And to help you do so, this article will share nine tips on improving your server management and fix some problem about windows, networking, cluster, batch-processing, .
I work at a company that maintains a network of about 200 Windows XP workstations, and several of them are on (locked or logged out) with an idle processor and 2GB of RAM that is just sitting there. I imagine many companies are in a similar situation, and I want to know is there software that can utilize these idle machines?
Many scripts I write handle work in batches, and these scripts can be executed on any machine… all the inputs, outputs, and even the programs are stored on network drives. What I want to do is design a service that, in short:
- runs on every machine
- accepts batch-processing commands
- runs them with a low resource priority
Does software like this already exist? I couldn’t find anything out there and maybe there is a reason for that, but it sounds like a great idea to me.
Sure. You’re talking about clustering.
You’re going to be a bit limited with Windows XP, unfortunately. It’s not really made for that sort of thing (whenever I cluster with XP, I serve XP as a terminal session to a linux desktop, it allows a lot more flexibility.)
Still, there is software out there. Check out BOINC, it’s got a lot of potential for what you’re talking about, and it runs on everything. (Did I mention it’s free? No? It’s free.)
Condor is one of the oldest I know of. Works with Unix and Windows hosts
You should check out GridGain
Since you are looking at running your own software, you could have it execute when the screensaver turns on. This will ensure it only runs when the PC is idle. You can use System ScreenSaver ($15) or Runsaver (free). After that, it would be up to you to handle the code that runs – since it is hosted over the network, you could configure the clients to all run the same executable, and then handle how the data is processed, what happens if the screensaver is interrupted, etc.