The forum will be unavailable for maintenance at some point from Friday, April 13 at 19:00 EDT until Sunday, April 15 at 23:59 EDT. Downtime will be minimized but the exact timing is unknown.

In the SQL Anywhere 12 - documentation ( says that:

Using dbping -s can be useful to give an indication of whether communication compression may improve performance.

Is there a formal (or heuristic) rule, which, depending on the "Total Time" & "Average" - values ​​of the "Round trip simple request", "Send throughput" & "Receive throughput" - parameters tells whether to use communication compression?

asked 26 Apr '13, 05:42

Ilia63's gravatar image

accept rate: 28%

edited 26 Apr '13, 07:49

Mark%20Culp's gravatar image

Mark Culp

No, I know of no such heuristic.

I'd guess if all of the following are true (and these are ballpark estimates):

  1. your send or receive throughput is slow (say 512KB per second or slower)
  2. you are dealing with blobs, fairly large values or medium to large result sets
  3. your data is fairly compressible
  4. both your client and server have available CPU (i.e. neither is already at 100% CPU)

then communication compression is likely to improve your performance. Note that I wouldn't recommend communication on a LAN. But the only way to know for sure is to try it.


Hope this helps.

permanent link

answered 29 Apr '13, 09:00

Ian%20McHardy's gravatar image

Ian McHardy
accept rate: 38%

edited 29 Apr '13, 09:03

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 26 Apr '13, 05:42

question was seen: 956 times

last updated: 29 Apr '13, 09:03