Forum Post: AW: by-reference q

  • Thread starter Thread starter Mike Fechner
  • Start date Start date
Status
Not open for further replies.
M

Mike Fechner

Guest
“Appserver message compression (-mc startup parameter). May or may not be worthwhile; compression/decompression algorithms have their own overhead to take into account which can nullify any benefit from sending compressed vs. uncompressed data. So benchmark before deciding when and where to use this.” For that reason it’s very handy that –mc is a client startup parameter. You can use it for remote WebClients where compression is likely to have a positive impact but not on local clients where –mc may just increase the CPU load. Von: Frank Meulblok [mailto:bounce-fmeulblo@community.progress.com] Gesendet: Mittwoch, 30. April 2014 13:13 An: TU.OE.Development@community.progress.com Betreff: RE: by-reference q RE: by-reference q Reply by Frank Meulblok As others explained, BY-REFERENCE will only work within a single instance of the AVM - either the AppServer client or the AppServer agent. Going from one to the other will always be by-value. If you're looking to gain performance in that scenario, you'll want to look into: - Schema marshalling (-ttmarshal startup parameter / SCHEMA-MARSHAL attribute of the temp-tables): cuts down the amount of metadata sent over the connection - Appserver message compression (-mc startup parameter). May or may not be worthwhile; compression/decompression algorithms have their own overhead to take into account which can nullify any benefit from sending compressed vs. uncompressed data. So benchmark before deciding when and where to use this. Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Back
Top