Mark Matthews wrote:
> Greg Steele wrote:
> > Hello,
> > I've been doing some experimenting with the
> > useCompression property that can be assigned
> to a
> > Connection. It appears that data sent from
> the
> > server is compressed, but date inserted from
> the
> > client is not. I'm transmitting some pretty
> large
> > files, and this could make a big difference.
>
> > Anybody know how to enable bidirectional
> > compression?
> >
> > My server is running MySQL 4.1, and I'm
> using
> > J/Connector 3.0.16.
> >
> >
> > Thanks!
>
> Greg,
>
> The compression automatically works in both
> directions. However, if the client determines that
> the data would take up more room compressed, then
> it sends the original data (which can happen with
> some files). It also doesn't compress packets
> below some threshold.
>
> Have you tried the same statements using the
> "mysql" command-line client with --compress
> enabled and looked to see what it is sending?
>
> -Mark
>
Greg,
Oops, I just looked, and there's some debug code that's been left in 3.0 that causes it to never compress outgoing packets (egg on face).
I've fixed this for 3.0.17 and 3.1.9. The change should be in the nightly snapshots after 00:00 GMT at
http://downloads.mysql.com/snapshots.php ... The files in question should have a date of May 03,2005 on them.
-Mark
Mark Matthews
Consulting Member Technical Staff - MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html