E10 Compression

Yahoo Archive
1
Thanks Erik :-)


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@…

http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?


On Thu, Sep 4, 2014 at 5:06 PM, ejohnson@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>The datasets (which take up the most bandwidth) in ERP 10 payloads are compressed by default. Â If you look in the web.config file and the binding configuration for net.tcp, you&#39;ll see &quot;NetTcpCompressedUsername&quot;, &quot;NetTcpCompressedWindows&quot;, etc. Â Which one is in use depends on whether you use Windows SSO or a username/password.</p>

We do our own serialization of datasets because the .NET version was a lot slower. Â As part of that process, we run them through the "deflate" compression library. Â Our tests showed that ERP 10 network consumption was a bit better than ERP 9 with compression enabled on both versions. Â Let me know if you are seeing otherwise.

This all applies to the client app or integrations running through the .NET proxies. For web services (SOAP), compression (and the custom serialization) are not enabled to stay interoperable.

</div>
 


<div style="color:#fff;min-height:0;"></div>

2
Guys,
In 9.05 we had the option to enable network compression between client and server. In E10 that option appears to not be available. Does anyone know if that exists in 10? Further more would enabling compression at the IIS level have any impact?


Thanks!


Jose C Gomez
Software Engineer



T: 904.469.1524 mobile

E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?
3
The datasets (which take up the most bandwidth) in ERP 10 payloads are compressed by default.  If you look in the web.config file and the binding configuration for net.tcp, you'll see "NetTcpCompressedUsername", "NetTcpCompressedWindows", etc.  Which one is in use depends on whether you use Windows SSO or a username/password.

We do our own serialization of datasets because the .NET version was a lot slower.  As part of that process, we run them through the "deflate" compression library.  Our tests showed that ERP 10 network consumption was a bit better than ERP 9 with compression enabled on both versions.  Let me know if you are seeing otherwise.

This all applies to the client app or integrations running through the .NET proxies. For web services (SOAP), compression (and the custom serialization) are not enabled to stay interoperable.