Hello, We're having a philosoph

[drosenkranz]

Hello,

We're having a philosophical discussion in terms of performance on where the EXE should be launched from, the server or the local user's hard drive.

Option #1 says that the EXE should be launched from the user's local hard drive. An update program on the user's machine checks the server for an updated version of the EXE. If the EXE on the server is newer (an update), then the file is first copied down to the local user's hard drive and then launched from their own hard drive. Whether an update occurs or not, the EXE is always launched from the local user's hard drive.

Option #2 says the EXE should reside on and be launched from the server.

All databases reside on the server for both options. We have 650+ users that may need to run one or more applications at a time.

Which option is the better choice in terms of performance & network resource usage?

Thank You For Both Your Time And Input,

Dave The 2nd mouse gets the cheese.

 

[Shurik]

it depends on what that exe does ... if after running it it makes local stuff then - run it from local comp ,
but if it works with the server , run it from there ,
that way you wan't need to manage the updates ...
anyway , if you have 650 users , move it locally if it is a heavy one ... Alex,
Problem? No Problem!
Drink more beer...

 

[JabbaTheNut]

We have created a login script that copies the EXE from the server to the users' hard drives when they log on to the network. This login script is targeted to specific groups so that the EXE is not distributed to everyone unnecessarily. This way all targeted users get the same update at the same time (i.e., next logon) and server performance is not hampered by the added network activity of users accessing the EXE on the server. I imagine, however, that, depending on the application, this could pose problems since some users who have not yet logged off since the EXE update was put in place will be using an older version of the EXE than those who logged in afterward. For us and our application, the above method works beautifully. Game Over, Man!

 

[jamk555]

Can you restrict logon hours say from 12:00AM to 11:58PM. Therefore forcing the user to log back-in after that 2 minute period therefore every morning the users would recieve the update when they log in?

Just a thought.....(Although it does not relate directly to your topic, I cant resist a philosophical discussion)

regards! jamk555

 

[electraboy]

Indeed, I would say: "It depends on what the application does". Is there a lot of traffic between a database and the application and is this only when started or every time a change is recorded ?

When the application very often contacts the database, it might be more performant to let it reside on the server, but otherwise.
Maybe try both and monitor your network... It is impossible to make anything foolproof because fools are so ingenious.

Murphy's Laws​