Sign in with
Sign up | Sign in
Your question

Run a program on a SERVER from the CLIENT PC.

Tags:
  • PCS
  • Servers
  • Business Computing
  • Network Drive
Last response: in Business Computing
Share
May 27, 2013 6:45:42 PM

I am setting up a clinic with 4 Client PCs and 1 Server (or MAIN-PC). The Client PCs are intel i3 boxes with Win 7 pro. The Server (Main-PC) is an i5 box with 8G RAM (Win 7 Pro). ALL connections are GIG. The server has a folder sitting on it which has been shared with all the client PCs. This folder also contains the exe file of the program that needs to run on all client PCs. On each of the client PCs, I have made a shortcut to this folder on the server so that I can run the program from all the client PCs. The program runs fine except it runs into a nasty lag every now and then and I have to restart the program then. The program runs fine on the server itself though.


    The question is that why do experience this lag on client PCs?
    Do I need SAS drive or RAID to make the performance better?
    If RAID, then is RAID 0 recommended? Do I really need it for this?
















More about : run program server client

May 27, 2013 7:04:25 PM

normally its recommended to run the programs directly on the client and just have the program look back to the server for the actual data.

e.g. MS word is installed on all computers, but the documents them selves reside on the server and accessed across the network.

What program is it your using, some programs will work as your describing them but others like you have found will run into issues.
m
0
l
May 27, 2013 7:19:47 PM

RAID 0 is not recommended at all for Servers,

if u need more hard drive speed, get SSD's for a small amount of fast storage (RAID 1)

if u need more again, establish a RAID 5 or 6 ( or 0 + 1)
m
0
l
Related resources
May 28, 2013 3:45:05 AM

Thanks for the reply. The software I am using is called Tracker (patient database). It is supposed to work the way I have set it up. It is typically not installed on the clients but the clients access the parent database sitting on the server. Even on the server it isn't truly "installed". It just sits there as a parent database ready to be accessed by the client PC. This typically doesnot even require RAID. Totally different animal from the way MS Office works.
m
0
l
May 28, 2013 11:17:21 AM

I have seen a few programs that work the way you are talking about. Usually the ones I have looked at are pretty basic and lightweight programs, and the data that they may need to be accessing is very small (few MB much less several GB in space.) Working with something so lightweight usually doesn't call for high-speed hardware like SSD RAID arrays, but it's never gonna hurt.

What kind of storage configuration do you have on your server anyways? Onboard SATA controller? Single drive or multiple, and what are the drive types? And how about memory? If you copy a large file (20+ GB) from the main computer onto one of the client computers, what kind of throughput are you getting on the network?

I've come across a similar issue previously where programs would stop responding properly across the network because of a power saving setting in the Control Panel which is easy to change and hopefully might be of some use for you. In the Power Options, make sure that your server is set to High Performance. You don't want the power saving features enabled on your server, it can cause problems. Now click Change Plan Settings, and open up the Advanced Power Settings. First take a look at the Hard Disk section and be sure to set "Turn Hard Disk Off After" to NEVER. Next, go to the Sleep section and set "Sleep After" and "Hibernate After" both to NEVER.

What I found was happening in the previous situation was that as the computer sat idle for a while, the hard drives would temporarily be suspended. Suddenly a client was sending requests for data to the server, but the hard drives were not up and running yet, which caused a lag. This lag can sometimes be very finicky with network connection timeouts as well as programs opening and running properly.
m
0
l
June 4, 2013 12:25:39 PM

If your setting this up for a business, get a real server. Your going to be the one on the hook when the system crashes. Look into terminal services and remoteappTS. Desktop machines are not made to perform under intensive i/o loads. The network connections cannot be teamed, your probably breaking an eula just by letting users use the program from a seperate client box, blah, blah, blah I could go on and on about what your doing wrong. Don't really see anything that your doing right.

Be a professional. Follow best practices. Don't get sued.
m
0
l
June 4, 2013 4:41:39 PM

While I definitely agree with umm@gumma, some software is specifically designed (and even their support specifically states using) in a shared network folder method like the OP is describing here.

There are a LOT of things that go into a business network, more than just the network, more than just the software and even the hardware. Even a small office has to follow suit with the proper requirements to protect information and follow all the rules and regulations. It's especially hard on small offices because those stringent requirements are often hard to implement on a limited budget and by unskilled technical labor. But it has to be done.

Terminal services is definitely something to look into to try and solve the issue, but the software vendor is going to be your main resource on this. What do they say to do? Your custom-built server may fit the needs for the time being, but it is not a long term investment. As stated above, you need a professional solution. There's a big difference between a standard desktop computer and a true business-class server.
m
0
l
!