maria-discuss team mailing list archive

[Rohan M C <rohanmc@xxxxxxxxx>]

Hi Frederico & Yoku,
Thanks for your responses!  Also, I had a question regarding the
environment in which you've been using compression- are they virtualized
instances or bare metal? Our db instances are m1.xlarge aws ec2 instances
(4 vcpu + 15G mem) and this is somewhat an unknown for us which is why
we're only moving some tables to compressed to try out- I'm just trying to
read up and find out as much as I can about compression and any pitfalls as
I can so that I can be better prepared- I am aware of the basic concepts
that it's more cpu intensive, but most of the material I've found states
that they're running on fusionio etc...so any insight/reading into running
on virtualized instances would help greatly

Jan,
We do have innodb_file_per_table set to 1. About your question - as I've
mentioned we've never used compression or barracuda before so we want to
tread lightly. Also considering that Antelope is the default file format, I
assumed that it was (possibly) stable/preferrable. Do you know if this is
the case?

Thanks,
Rohan

On Wed, Oct 29, 2014 at 2:14 AM, yoku ts. <yoku0825@xxxxxxxxx> wrote:

> Setting innodb_file_format Barracuda needs innodb_file_per_table.
> So, your (new created) Barracuda table is putted into one .ibd file.
> Any other your Antelope tables (in other .ibd files or ibdata1) don't be
> affected that operation.
>
> I have mix of Antelope/Barracuda for years in our production environment
> too, without any problem of that.
>
> Regards,
>
> 2014-10-29 17:35 GMT+09:00 Federico Razzoli <federico_raz@xxxxxxxx>:
>
>> I had a mix of Antelope/Barracuda for years. As far as I can tell, this
>> never caused problems.
>>
>> Regards
>> Federico
>>
>>
>> --------------------------------------------
>> Mer 29/10/14, Rohan M C <rohanmc@xxxxxxxxx> ha scritto:
>>
>>  Oggetto: [Maria-discuss] question regarding innodb compression
>>  A: maria-discuss@xxxxxxxxxxxxxxxxxxx
>>  Data: Mercoledì 29 ottobre 2014, 08:36
>>
>>  Hi
>>  all,
>>  Due to space constraints we are considering the
>>  innodb compression option for some of our larger tables.
>>  We're not compressing all the tables, but only a select
>>  few to begin with. Our current planned process for this is
>>  to SET GLOBAL innodb_file_format=Barracuda;
>>  create compressed table, transfer data,  and switch
>>  innodb_file_format back to Antelope.
>>  My question is around having this mix of table
>>  file formats in the same database. I've tried test
>>  queries and they were fine, but is it ok to have a mix of
>>  both Antelope and Barracuda file format tables in the db for
>>  a production environment?
>>  Thanks,Rohan
>>  -----Segue allegato-----
>>
>>  _______________________________________________
>>  Mailing list: https://launchpad.net/~maria-discuss
>>  Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
>>  Unsubscribe : https://launchpad.net/~maria-discuss
>>  More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~maria-discuss
>> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~maria-discuss
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~maria-discuss
> Post to     : maria-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-discuss
> More help   : https://help.launchpad.net/ListHelp
>
>