Hi, I have a question on maximum conccurent users. Lets assume that my database has reach it's peak for concurrent users.. Does this mean that the MySQL database is corrupted until I increase my server specs, or can my users reload the page and retry to input the data again? -Sam
It doesnt mean it is corrupted simply that the SQL statement wont have been executed - assuming all elements of the updates/ deletions etc are done in a single connection. They can certainly re-enter the data and resubmit and assuming the number of connections are now below the max but that all depends what your error handling is like.
Is there a terminology name for this process of "error handlng" ? - Also what constitutes as a concurrent user? For example on a php/mysql board.. If somebody is simply just reading a post, does this make them a concurrent user? How about if they are in the process of writing a post? Thanks In Advance, - Sam
Concurrent simply means at the same time and user is in relation to the db not the site so it is the number of people that are connecting to the db at the same time. In the process of writing a post wont be a db user nor someone actually reading posts however actually submitting the new post or requesting a page will make them a user. You need to look at how well coded the db interactions are... firstly are the connections being closed after the command is executed? Secondly is there error handling so that the connection is closed if an error occurs? Thirdly is the db being used efficiently? Poorly written scripts will make multiple connections to do what should have been done in a single connection. Error handling is the correct terminology for it - in MS languages it is typically done by Try... Catch.... Finally