I'm doing at least 2x that volume, plus running a very active mail server, and I've never seen that problem.
Did you try duplicating it with other links? Seeing if you can create the problem by hitting the link twice in a row?
If you have a log program, and you can find when your buisiest time of day is, try it then, beating up your links to see if you can duplicate it.
I have a hard time believing it's a MySQL problem. I could imagine this sort of problem if it was due to simultaneous access (like flat-file access locking).
If the jump.cgi was modified, or if your indexes were modified, then you'd expect to be able to reproduce the problem repeatedly.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Did you try duplicating it with other links? Seeing if you can create the problem by hitting the link twice in a row?
If you have a log program, and you can find when your buisiest time of day is, try it then, beating up your links to see if you can duplicate it.
I have a hard time believing it's a MySQL problem. I could imagine this sort of problem if it was due to simultaneous access (like flat-file access locking).
If the jump.cgi was modified, or if your indexes were modified, then you'd expect to be able to reproduce the problem repeatedly.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
