Re: [Nagios-devel] NDO - why not innodb?
Posted: Mon Aug 20, 2007 8:11 am
------=_Part_27595_1518469.1187626285196
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/8/07, Alessandro Ren wrote:
>
>
> I just would like to know the reason that the NDO DB uses myisam
> engine and not Innodb. If it is because of performance issues?
> It seems to me that innodb would be better in the long run, having
> huge databases, am I missing something?
> Thanks.
Greetings,
I just wanted to throw in a tip, since this bit me this morning. If you're
going to use innodb for your tables, I would suggest using this option in
your configuration:
innodb_file_per_table
This creates per table tablespaces (just like MyISAM does), instead of one
large shared tablespace (which is the default). The reason this is nice is
because innodb tablespaces only grow. To "shrink" a tablespace, you have to
dump all tables, delete the tablespace file, and re-import your data. This
can be a huge process on databases with large tables (which I just had to do
this morning). I'm not a DB administrator and this may not be ideal for
certain environments, but it seems wise to do when you have large tables
that may be purged from time to time. If your tables only need to grow, then
it might not be an issue.
Brendon
------=_Part_27595_1518469.1187626285196
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/8/07, Alessandro Ren <[email protected]> wrote:
I just would like to know the reason that the NDO DB uses myisamengine and not Innodb. If it is because of performance issues? It seems to me that innodb would be better in the long run, havinghuge databases, am I missing something?
Thanks.Greetings,I just wanted to throw in a tip, since this bit me this morning. If you're going to use innodb for your tables, I would suggest using this option in your configuration:
innodb_file_per_tableThis creates per table tablespaces (just like MyISAM does), instead of one large shared tablespace (which is the default). The reason this is nice is because innodb tablespaces only grow. To "shrink" a tablespace, you have to dump all tables, delete the tablespace file, and re-import your data. This can be a huge process on databases with large tables (which I just had to do this morning). I'm not a DB administrator and this may not be ideal for certain environments, but it seems wise to do when you have large tables that may be purged from time to time. If your tables only need to grow, then it might not be an issue.
Brendon
------=_Part_27595_1518469.1187626285196--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/8/07, Alessandro Ren wrote:
>
>
> I just would like to know the reason that the NDO DB uses myisam
> engine and not Innodb. If it is because of performance issues?
> It seems to me that innodb would be better in the long run, having
> huge databases, am I missing something?
> Thanks.
Greetings,
I just wanted to throw in a tip, since this bit me this morning. If you're
going to use innodb for your tables, I would suggest using this option in
your configuration:
innodb_file_per_table
This creates per table tablespaces (just like MyISAM does), instead of one
large shared tablespace (which is the default). The reason this is nice is
because innodb tablespaces only grow. To "shrink" a tablespace, you have to
dump all tables, delete the tablespace file, and re-import your data. This
can be a huge process on databases with large tables (which I just had to do
this morning). I'm not a DB administrator and this may not be ideal for
certain environments, but it seems wise to do when you have large tables
that may be purged from time to time. If your tables only need to grow, then
it might not be an issue.
Brendon
------=_Part_27595_1518469.1187626285196
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On 8/8/07, Alessandro Ren <[email protected]> wrote:
I just would like to know the reason that the NDO DB uses myisamengine and not Innodb. If it is because of performance issues? It seems to me that innodb would be better in the long run, havinghuge databases, am I missing something?
Thanks.Greetings,I just wanted to throw in a tip, since this bit me this morning. If you're going to use innodb for your tables, I would suggest using this option in your configuration:
innodb_file_per_tableThis creates per table tablespaces (just like MyISAM does), instead of one large shared tablespace (which is the default). The reason this is nice is because innodb tablespaces only grow. To "shrink" a tablespace, you have to dump all tables, delete the tablespace file, and re-import your data. This can be a huge process on databases with large tables (which I just had to do this morning). I'm not a DB administrator and this may not be ideal for certain environments, but it seems wise to do when you have large tables that may be purged from time to time. If your tables only need to grow, then it might not be an issue.
Brendon
------=_Part_27595_1518469.1187626285196--
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]