Kbase P93697: Performance slowdown using the AppServer after migration from 9.1D to OE10 when using temp-table par
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/15/2010 |
|
Status: Verified
SYMPTOM(s):
Performance slowdown using the AppServer after migration from 9.1D to OE10 when using temp-table parameters
Increased AppServer network bandwidth usage
Performance slow with AppServer usage
Using temp-tables parameters with AppServer
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CHANGE:
Upgraded from Progress version 9 to OpenEdge 10
CAUSE:
Changes in how temp-tables are managed result in more temp-table schema information to be sent over the network by default in OpenEdge 10.
By default, all available schema information including field formats etc. is sent over the network. The difference between Progress 9 and OpenEdge 10 is that in Progress 9 not all information is available unless the RCODE-INFORMATION option is used, so less information would be sent in most cases. In OpenEdge 10, the full schema information is always available.
FIX:
OpenEdge 10 also introduces the ability to control how much schema information should be marshaled over the network.
The -ttmarshal startup parameter is used to specify the default schema marshaling behavior for the session using the syntax:
-ttmarshal n
Where n is a value between 0 and 4.
The default is 0, which means full schema information is sent.
The value of 2 means minimal schema is sent for both static and dynamic temp-tables; this is equivalent to Progress 9 behavior in most cases.
The temp-tables now have a SCHEMA-MARSHAL attribute to set the marshaling to FULL, MIN, or NONE is for specific tables. MIN is the equivalent to Progress 9 behavior without the RCODE-INFORMATION option, FULL is the equivalent to Progress 9 behavior with the RCODE-INFORMATION option.