Nice one Johan, thanks for the info.
On Tue, Oct 4, 2011 at 2:17 PM, Johan De Meersman wrote:
> As noted in the title, I'm messing about a bit with InnoDB compressed
> tables. As such, I found a rather glaring hole in the Internet: how the hell
> do you turn compression off again?
As noted in the title, I'm messing about a bit with InnoDB compressed tables.
As such, I found a rather glaring hole in the Internet: how the hell do you
turn compression off again? :-D
After messing about a lot and googling until my fingers hurt, I happened upon
this bug report:
" I am still benchmarking, but I see a 15-20% performance gain after
enabling compression using bacula gui (bat)."
This is a very good performance improvement and how much disk space did you
saved here ?
Can you do bench marking with 4kb and 8kb key_block_size as well to check
what
Am 14.09.2011 14:50, schrieb Maria Arrea:
> I have finally enabled compression:
> I am still benchmarking, but I see a 15-20% performance gain after enabling
> compression using bacula gui
as expected if disk-io is the only bottenleck
the same with NTFS-Compression inside a VMware M
I have finally enabled compression
Am 14.09.2011 09:50, schrieb Maria Arrea:
> I have read all your mails, and still not sure if I should enable innodb
> compression
if you have enough free cpu-ressources and IO is your problem simply yes
because the transfer from/to disk will be not so high as uncomp
The server hosting bacula and the database only has one kind of disk: SATA,
maybe I should buy a couple of SSD for mysql.
I have read all your mails, and still not sure if I should enable innodb
compression. My ibfile is 50 GB, though.
Regards
Maria
Questions:
1) Why are you putting
Thanks for correcting me in the disk stats Singer, A typo error of SSD
instead of SAS 15k rpm.
Compression may not increase the memory requirements :
To minimize I/O and to reduce the need to uncompress a page, at times the
buffer pool contains both the compressed and uncompressed form of a
my.cnf is
> attached below:
>
>
> These are my questions:
>
>
> - We have real slow storage (raid 6 SATA), but plenty CPU and ram . Should
> I enable innodb compression to make this mysql faster?
> - This system is IOPS-constrained for mysql (fine for backup, though).
GB in a couple of weeks, and I
will change my.cnf to reflect more memory. My actual my.cnf is attached below:
These are my questions:
- We have real slow storage (raid 6 SATA), but plenty CPU and ram . Should I
enable innodb compression to make this mysql faster?
- This system is IOPS-constra
Hi,
Giorgio Zarrelli wrote:
Hi,
I saw that to enable server/client protocol compression I can start mysql with
the "-C" option.
Is there a configuration keyword to write in my.cnf to enable server/client
protocol compression?
Yes. In general, most command-line options can
Hi,
I saw that to enable server/client protocol compression I can start mysql with
the "-C" option.
Is there a configuration keyword to write in my.cnf to enable server/client
protocol compression?
Thanks
Giorgio Zarrelli
--
MySQL General Mailing List
For list arch
On 28.05.2007 18:34 CE(S)T, Kevin Hunter wrote:
> At 5:45a -0400 on 28 May 2007, Yves Goergen wrote:
>> Also, URLs sometimes contain things like
>> session IDs. They're probably not of interest for my use but it's not
>> always easy to detect them for removal.
>
> Really? Why wouldn't it be easy
At 5:45a -0400 on 28 May 2007, Yves Goergen wrote:
> On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote:
>
>> In particular, I imagine a lot of the HTTP requests would be the
>> same, so you could create a table to store the requested URLs, and
>> then have a second table with the timestamp and foreign
Yves Goergen wrote:
On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote:
At 12:31a -0400 on 28 May 2007, Dan Nelson wrote:
You want the ARCHIVE storage engine.
http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html
Hm, it doesn't support deleting rows and it cannot use indexes. So doi
On 28.05.2007 09:06 CE(S)T, Kevin Hunter wrote:
> At 12:31a -0400 on 28 May 2007, Dan Nelson wrote:
>> You want the ARCHIVE storage engine.
>>
>> http://dev.mysql.com/doc/refman/5.0/en/archive-storage-engine.html
Hm, it doesn't support deleting rows and it cannot use indexes. So doing
statistics o
y day. Older log files are compressed by month,
>> with bzip2. This gives a very good compression ratio, since there's a
>> lot of repetition in those files. If I store all that in a regular
>> table, it would be several gigabytes large. So I'm looking for a way
>>
This gives a very good compression ratio, since there's a
> lot of repetition in those files. If I store all that in a regular
> table, it would be several gigabytes large. So I'm looking for a way
> to compress the database table but still be able to append new rows.
> As the n
Hi,
I'm thinking about using a MySQL table to store an Apache access log and
do statistics on it. Currently all access log files are stored as files
and compressed by day. Older log files are compressed by month, with
bzip2. This gives a very good compression ratio, since there'
Thank you for the ideas. Very helpful.
Thanks
Emery
- Original Message -
From: "Danny Haworth" <[EMAIL PROTECTED]>
To: "Director General: NEFACOMP" <[EMAIL PROTECTED]>
Sent: Thursday, October 09, 2003 12:01
Subject: Re: Ideas on Compression Protocol
&g
Hi group,
I recently asked about Compression and security and got nice answers.
Now I have got a different question:
What are the disadvantage of using that client/server Compression protocol?
Does it increase speed? Does it decrease speed? Does it overload the server? The
client?
Any ideas
ffic, like you would get when
trying to decompress a 10k part of a large zip file.
hth
danny
On Tue, 2003-10-07 at 10:49, Director General: NEFACOMP wrote:
> Hi group,
>
> I have read in the MySQL manual that the client/Server Compression protocol adds
> some security to the applica
> Hi group,
>
> I have read in the MySQL manual that the client/Server
> Compression protocol adds some security to the application.
>
> Does anyone have more information on this?
>
It adds security by compressing the network trafic, which is more security
by obscurity,
Hi group,
I have read in the MySQL manual that the client/Server Compression protocol adds some
security to the application.
Does anyone have more information on this?
Thanks,
__
NZEYIMANA Emery Fabrice
NEFA Computing Services, Inc.
P.O. Box 5078 Kigali
Office
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitry Kosoy wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 10:55 AM
To: Dmitry Kosoy
Subject: Re: compression protocol
Your message cannot be posted because it appears to
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 18, 2002 10:55 AM
To: Dmitry Kosoy
Subject: Re: compression protocol
Your message cannot be posted because it appears to be either spam or
simply off topic to our filter. To bypass the
Sommai,
Wednesday, February 06, 2002, 8:01:13 AM, you wrote:
SF> Hi,
SF> I need to know that MySQL has any compression method when it store
SF> data? If the answer is Yes, How the different compression between MySQL
SF> and other tools (zip, gzip)? I asked this questi
Sommai,
Wednesday, February 06, 2002, 8:01:13 AM, you wrote:
SF> Hi,
SF> I need to know that MySQL has any compression method when it store
SF> data? If the answer is Yes, How the different compression between MySQL
SF> and other tools (zip, gzip)? I asked this questi
Hi,
I need to know that MySQL has any compression method when it store
data? If the answer is Yes, How the different compression between MySQL
and other tools (zip, gzip)? I asked this question because I need to store
some text file for future used (at least 1 Mbyte per day). I was
Look up myisampack in the mysql manual at http://www.mysql.com/doc/. The
only drawback is you can't modify the table.
> I have a table that has massive amounts of text. Just plain text, stuff
> that would compress REALLY well. Does mysql have any sort of compression
> internally
I have a table that has massive amounts of text. Just plain text, stuff
that would compress REALLY well. Does mysql have any sort of compression
internally for the table data that it stores? A simple gzip wouldn't add
too much overhead to the system, and you could still have clear
On Tue, 12 Jun 2001, Emiliano F Castejon (Castle John) wrote:
> I would like to know if there is a way to use a compressed MYSQL bank
> for read and write (dynamic compression/decompression).
I'm not sure if it is possible to do this natively in MySQL; I'll let
someone else a
I would like to know if there is a way to use
a compressed MYSQL bank for read and write (dynamic
compression/decompression).
Using "myisampack" utility I can only create a
read-only bank.
Is there any internal compression scheme
in MySQL ?
Disk space is an important factor in my
w
Is it possible to enable compression between replicating database servers?
I'm assuming that there is already compression code in place, because of
the need to link with the compression libraries on the client end
sometimes.
Compressing the replication connection has certain advantages wher
"Apolinaras \"Apollo\" Sinkevicius" writes:
> I wonder, is there a performance gain if compression is turned on the
> client side?
> My set-up:
> Front end: M$Access97 via latest MyODBC
> Back end: MySQL 3.23.30 on RH7 with PIII300 128Ram
>
I wonder, is there a performance gain if compression is turned on the
client side?
My set-up:
Front end: M$Access97 via latest MyODBC
Back end: MySQL 3.23.30 on RH7 with PIII300 128Ram
LAN is 100BaseT Full Duplex switched.
Thanx
36 matches
Mail list logo
