Do you have a question? Post it now! No Registration Necessary. Now with pictures!
August 26, 2009, 9:10 pm
rate this thread
I have a major performance issue with an application that is inserting
strings into a mysql database.
I'm not quite sure but we see major backlogs and it's only about 6MB
that it would be inserting in 24 hours. That should not be a major
problem i would say.
The way this logserver is working is:
send message off to syslog on port 1515 which is on the same host.
/*message parsing with strtok and other standard C function calls.*/
sprintf(query,"insert into logs(source,date,time,program,msg)values
cout << "INSERT Query: " << query <<
This seems to insert only one message per about 500 to 800ms
(estimated). Each message would be around 200 Bytes long. Sometimes
there's multiple messages arriving per second asynchronously.
My problem is, I can not do too much debugging and 'trying things' on
this because this is a system that's been switched live already. My
local system does not seem to be experiencing the same performance
Any clues where bottle necks may be and how they can be resolved?
Thanks a lot!
PS: mysql --version
mysql Ver 14.12 Distrib 5.0.54, for pc-linux-gnu (i486) using
September 1, 2009, 6:43 pm
Re: major performance issue
Are those MyISAM tables?
In all likelihood the inserts are backing up behind selects - very common
on a live system. On your test rig there were probably hardly any selects
and so the inserts had the access to tables all by themselves. Selects
ahead of inserts actually strikes me as pretty normal and even rather
desirable priority on a live system.
on the other hand, you can always try "INSERT HIGH_PRIORITY" though in
this case you'd have to make sure there are no concurrent inserts from
- » Americanas.com SALDO de TVs Com at 80% de Desconto (29798)
- — Newest thread in » MySQL Database Forum
- » ssh on command line: force using a group size (prime size) of 1024 (and no...
- — The site's Newest Thread. Posted in » Secure Shell Forum