It will depend upon your situation. Compression is just a tool
and when to use it will depend upon your situation and it would
be something the site's I.T. staff should review to help measure
what (if any) effects and benefits it will actually have in your
specific settings.
You will want to review the points made on this documentation page:
http://dcx.sybase.com/1101en/dbadmin...n-perform.html
the paragraphs for
"Enabling compression"
and
"Modifying the compression threshold"
covers much of this terrain.
One can always run with it on all the time and that may have some
impact on preserving you local bandwidth (something that is not
explicitly discussed in the above referenced page) but that would
be more typical of an I.T. policy type decision. In many cases if
the LAN networks involved are relatively unsaturated this setting
may have no significant net benefit.
Quote:
Why it is not checked by default ? |
If you make this decision for a broad customer base, you may
end up penalizing your customer that have minimal host/client
machines. This may also tend to penalize some customers that are
embedding our software embedded in an application; which is
potentially a large percentage of our customer base.
There is some memory and CPU overhead involved that
may upset the default performance for some customers if
we silently switched to it during a software upgrade. For
backward compatibility the default has always been off
so it makes sense to preserve that unless there is an
over-arching reason to change that.
"Bofcilo" <sprintrz (AT) gmail (DOT) com> wrote
Quote:
ODBC driver for SA 10 has check box <<Compress network packets
Help for this option :
Compress network packets Select this option to turn on compression
for the connection. Using compression for a connection can
significantly improve SQL Anywhere performance under some
circumstances.
Use or not ? When ? Internet connection ? Slow connection ? Why it is
not checked by default ? |