here is a network performance question I want to put on you, because I do not have enough experience on this matter.
When searching the web for "network + performance + queries" or something simliar, they are all discussing SQL servers.
In my case though, I have an application on windows in a local network, using wxWidgets file objects, eg.:
Code: Select all
wxFileName fn ("\\\\172.16.x.x\\test\\exchange.txt");
if(fn.Exists())
{
wxFileConfig *fc_file = new wxFileConfig(GetAppName(), wxEmptyString, fn.GetFullPath(), fn.GetFullPath(), wxCONFIG_USE_NO_ESCAPE_CHARACTERS);
//...
}Or I am watching a directory on the server like this:
Code: Select all
wxArrayString as_files;
wxDir::GetAllFiles(ms_path.GetFullPath(), &as_files, "*.dat", wxDIR_FILES);
if (as_files.GetCount() > 0)
{
for (int i = 0; i < as_files.GetCount(); i++)
{
//so something
}
}Now, every computer in the local network is querying the server with these file operations with a timer and Im asking myself:
How much delay should the timer have?
If realtime is of no importance, I could use something like 10000ms, but what if I would like a quicker response, if the user is waiting for a return value? Like 500ms?
Testing this with the few machines in my local network is no problem, but I can't simulate a setting like one server for several 100 client PCs.
Do you have any experience, which delay for a greater network is still decent and doesn't shut down all other network communication?
[EDIT:] The setting, where my app is running, may differ from rather primitive networks with a handfull of PCs plugged into another PCs, which they call the "server" - to other settings, where there might be running a real (MS) Server and several hundered machines configured and controlled by rigid admins.
Thanks
Natu
