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, instead of
"INSERT" I made an external file and then a "LOAD DATA". The difference
between both methods is great.
Hope this will be useful.
Best regards.
> ----------
> De: Raf Geusens[SMTP:[EMAIL PROTECTED]]
> Enviado el: martes 8 de mayo de 2001 14:27
> Para: [EMAIL PROTECTED]
> Asunto: Performance MySQL with C-API
>
> 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 quite sure
> actually) that the MySQL database is the bottleneck because it's a slow
> consumer. Now if I use a benchmark to check how many inserts the database
> can handle each second is will that result be about the same as the
> number of inserts the same database can handle using the C API? I guess
> not. Using a MySQL server on a machine with a 1000 mhz AMD processor I can
> 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.
>
> Greetings,
> Raf
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
