The current routine to load the player data first attempts an Insert at normal priority and then a select at low priority. I believe this to be backwards, selects can happen concurrently in
the database but inserts and updates lock the table so only one my occur at a time. This is especially a problem, when 80% or so of the people in a server were there the last round and thus have entries in the database already. Evidence of this problem is the full minute that is required to load player data at the beginning of a round.
I believe select should be attempted first and then, if no records are returned, should an insert be tried.

Please find attached my rewrite of that section, if you find any errors please let me know. I am new to source pawn.

Jon

PS, I tried to sign up to the bug ticketing system, never got an email.

Any more suggestions that will slow down the development of War3source binaryblade?

I still am trying to recover population peaks from the "suggestion" you made and all the crashes its caused.

Oh? I see, I am the ignorant one…

You know nothing of coding with PAWN and you came in here with a half-assed idea that created more problems than it solved (it did not solve any problems). Just because you read the Sourcepawn Wiki does not give you merit on making suggestions or in your case, guesses on what will work.

You have done nothing but slow the progress down of War3source. In fact, if you stop and did nothing, you would be more beneficial to everyone.

In fact, I told you this from the beginning.