Kbase P12666: Good practices to reduce the amount of network traffic between the WebSpeed transaction servers and
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/24/2009 |
|
Status: Verified
GOAL:
Good practices to reduce the amount of network traffic between the WebSpeed transaction servers and the remote file server
GOAL:
How do I minimize traffic between transaction server and file share?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
In the case WebSpeed transaction server and application code are on different machines on the network
- Increasing -mmax and -D would increase the amount of memory and number of entries for r-code caching.
- If application changes may be considered, persistent procedures can be loaded onto memory once an reused many times saving some overhead. Using a persistent procedure library instead of procedures defined inside include files can significantly reduce the resulting r-code size, therefore network traffic on this case. These libraries could be loaded as super procedures for transparency. - This is something that we could do on the framework with includes like cgiutils.i as well.
- .pl files can be helpful too.
- Most customers prefer not to use a file-server to host application code for WebSpeed or AppServer brokers because they can potentially process thousands or millions of requests so having the r-code on the same server improves performance. To maximize the performance this approach should be considered. A simple file-system replication mechanism should make version control simple.