use case -- queuing up a lot of INSERTS

[gerg]

Hi, I've checked out Q4M and it seems like a nice solution for my
problem, but I thought I'd check here first.

I have to do a lot of simple INSERTs into a table that are slow
because of indexing, overhead, etc. I'd like to INSERT first into a
queue table with Q4M then batch INSERT multiple rows into my table.
Does this make sense? What is the easiest way to do it with Q4M?
Thanks.

[Kazuho Oku]

Hi,

Unfortunately currently it is impossible to atomically acquire
ownership of more than one rows from Q4M. Thus it would be difficult
to use Q4M for such purpose.

IMHO, the best way would be to rely on the "group commit" feature
provided by some storage engines. With group commit, insertion
performance will (theoretically) scale as the concurrency increases.
InnoDB is one of the engines that support such feature, although there
is a problem when used together with binlog enabled. (see
http://www.mysqlperformanceblog.com/2006/05/19/group-commit-and-xa/)

2008/6/28 gerg <gregd...@yahoo.com>:

--
Kazuho Oku