is it really a slow query?

[kante]

problem description:
i have a web site and i want to print out elements on page request. Any time i print an element i like to update the record of his impression count. For statistic purpose.

The implementation:
a mySQL table (id INT primaryKey, name VARCHaR, count INT)

when i print with PHP the element i call a MYsql query like this

insert into myTBL (id, count) VALUES (x , y) ON DUPLICATE KEY y=y+1

MY host provider says
the above query looks like to affect webserver performance.

Well i execute this query about ten times before loading page , but this was supposed to be a real simple query...i go for update a specific id. So How come? It has it's own index (id) .... do you know a better way to perform this?

Thanks

[dagon]

doesn't look like it should be particular resource hogging, one option is to only run it once per page, you can gather the x,y values and just call it at the end. I would also do some basic benchmarking

[bradgrafelman]

I would tell your host provider to prove it by supplying you with the slow query log entries that suggest the above query is the culprit for any slowdowns.

[kante]

how much time to consider a query slow?

[dagon]

kante;10976419 wrote:

how much time to consider a query slow?

long_query_time is 10 seconds by default, if thats what you are asking