- a hot backup tool for InnoDB which also backs up MyISAM
tables
http://www.innodb.com/order.php
- Original Message -
From: "Jan Kirchhoff" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, January 31, 2006 1:09 PM
Subject: Re: Performance of MEMORY
ff" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.myodbc
> Sent: Tuesday, January 31, 2006 1:09 PM
> Subject: Re: Performance of MEMORY/HEAP-tables compared to mysql-cluster?
>
>
> > Hi,
> >
> > I am currently experiencing trouble getting my new mysql
also backs up MyISAM
tables
http://www.innodb.com/order.php
- Original Message -
From: "Jan Kirchhoff" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Tuesday, January 31, 2006 1:09 PM
Subject: Re: Performance of MEMORY/HEAP-tables compared to mysql-cluster?
Hi,
I am currently experiencing trouble getting my new mysql 5-servers
running as slaves on my old 4.1.13-master.
Looks like I'll have to dump the whole 30GB-database and import it on
the new servers :( At this moment I
do no see any oppurtunity to do this before the weekend since the
longest
sheeri kritzer schrieb:
No problem:
Firstly, how are you measuring your updates on a single table? I took
a few binary logs, grepped out for things that changed the table,
counting the lines (using wc) and then dividing by the # of seconds
the binary logs covered. The average for one table was
No problem:
Firstly, how are you measuring your updates on a single table? I took
a few binary logs, grepped out for things that changed the table,
counting the lines (using wc) and then dividing by the # of seconds
the binary logs covered. The average for one table was 108 updates
per second.
Kirchhoff
Cc: mysql@lists.mysql.com
Subject: Re: Performance of MEMORY/HEAP-tables compared to mysql-cluster?
Why are you using a heap table?
My company has tables with much more information than that, that get updated
much more frequently. We use InnoDB tables, with very large buffer sizes
and
sheeri kritzer schrieb:
Why are you using a heap table?
We started out with a myisam-table years ago when the table was much
smaller und less frequently updated. We tried innodb about 2 or 3 years
ago and couldn't get a satisfying result. We then changed it to HEAP and
everything was fine.
Why are you using a heap table?
My company has tables with much more information than that, that get
updated much more frequently. We use InnoDB tables, with very large
buffer sizes and have tweaked which queries use the cache and which
don't, on a system with lots of RAM (10Gb). Basically we've
a cluster would not necessarily give you speed but would give you
scalability, basically it increases your concurrency at which you can
service clients, also in your case the lockups are occuring because of
the obvious reason that the threads are competing for the system
resources, so a cluster may
Hi,
Did anybody ever benchmark heap-tables against a cluster?
I have a table with 900.000 rows (40 fields, CHARs, INTs and DOUBLEs,
Avg_row_length=294) that gets around 600 updates/sec (grouped in about 12
extended inserts a minute inserting/updating 3000 rows each).
This is currently a HEAP-ta
11 matches
Mail list logo
