200 connections & table locks a second is good performance, isn't it?
what you also can do is insert bunches of data, so instead of inserting each record
seperately, you just collect them and insert them at once like:
insert into mytable (field1, field2) values (1,2), (3,4), (5,6), (7,8), .. (n
Hello,
I don't know whether this is a solution for you or not, but I had to
insert a lot of registers ( about 14.000.000 ) and in a first instance I
tried to do it via "INSERT"; the response was not as fast as I needed (I
don't currently have de data here). I changed the approach and, inst
>
> Hi,
>
> I've got a couple a questions concerning the speed of insert queries when
> using the C API from MySQL. I've written an application that receives
> data through a CORBA event channel and stores it in a MySQL database. The
> problem is that a lot of events are dropped. I think (I'm qu
> Could you have a better disk environment on the Solaris machine versus the
> win32-machine?
The Solaris machine was a little bit slower executing the query, but it runs
as a production-webserver and there is much more load on it than on my
win32-test-machine.
> query that inserted 1 string
PROTECTED]]
Sent: Tuesday, May 08, 2001 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Performance MySQL with C-API
> insert 200 strings + timestamps a second through the API. Does that sound
> too less or am I expecting too much? Do benchmarks or test results for the
> C API exist? If someone
> insert 200 strings + timestamps a second through the API. Does that sound
> too less or am I expecting too much? Do benchmarks or test results for the
> C API exist? If someone has more experience on this or knows a place where
> I can find out more, plz let me know.
I just ran this test on a
