Quote:As usual I want more.
I avoided running Sesame in Client Server for a long time because I was so fearful about all the hassles to set it up and configure it. What a dummy I was for waiting! It was the simplest easiest task I have ever done. Less then 10 minutes start to finish getting the server and 5 clients working flawlessly.
Now that my fears of Sesame in client server have been proven foolish I want to manipulate the equipment I have to best work with sesame so I need more information.
In a windows network environment:
Should I have the Sesame server or client running on the machine with the most memory?
Server.
Quote:Should I have the Sesame server or client running on the machine that has the hard drive with the fastest seek rate?
Server again.
Quote:also I may have misunderstood this but, In prior posts I believe it was mentioned that it could be beneficial to have a database already accessed from a dummy client. I believe this was because once the data is accessed other clients connect to it quicker. Is this correct? if so should a specific form be accessed or just open the application?.
The only access that requires the database to load is the first access. That is why some folks like to pre-load the application. Once it is loaded, it does not matter which forms or databases are opened.
Quote:Until setting up a Linux server are there other tweaks that should or could be done to improve Sesame performance on a basic windows network.
Sesame is server heavy - meaning that you want the server to be as powerful as possible. If you can, try to free up memory on the server form Sesame's use, by eliminating processes and applications that you do not directly need. Also make sure that the swap file is pre-allocated - do not use dynamic allocation. Set the swap file as large as you can afford (at least twice physical memory). After you are up and running and activity is "typical" - check to see if the Sesame server is swapping. If so, add more RAM.
Also, the Sesame server is multithreaded. That means that, if provided with more than one CPU, Sesame server will take advantage of the additional power in an almost linear way.
If you can, try to optimize network access bottlenecks. For example, making the Sesame server that same machine you are using to be a file server (under MS) will route all of your traffic to the narrowest point. Try to distribute your network load as widely as possible. Try to use switches instead of hubs.
Clients need not be very powerful at all. There are only a handful of operations that can tax the client computer.
Quote:Thanks.