D.Cook
Member
Our Progress client application is pretty data-intensive, and therefore network-intensive. Generally this isn't a big issue for local networks, but when clients want to deploy the application over a remote network, they sometimes run into serious performance problems.
I'm talking about capable fibre links that are reported to be only a small percentage used. So I wonder if anybody else has had to deal with this, and if they have any tips for diagnosing the bottle-neck.
Is Progress network traffic different to other types (like http, smb, etc..)?
Where should a network administrator be looking to determine the bottle-neck?
And are there any recommendations on client startup parameters for this kind of environment?
I'm aware that we should be trying to 'thin' down our 'fat' clients, that is something we are working on in the long term..
I'm talking about capable fibre links that are reported to be only a small percentage used. So I wonder if anybody else has had to deal with this, and if they have any tips for diagnosing the bottle-neck.
Is Progress network traffic different to other types (like http, smb, etc..)?
Where should a network administrator be looking to determine the bottle-neck?
And are there any recommendations on client startup parameters for this kind of environment?
I'm aware that we should be trying to 'thin' down our 'fat' clients, that is something we are working on in the long term..