[hleV]

The only things you can do at this point are:

1. Get a faster MySQL server/closer to your game server for faster queries
2. Re-design plugin logic to not require saving upon disconnect
3. Improve the query to update multiple rows at once (so on server_changelevel() you would build a big query to save everything, and then don't do any queries on client_disconnected() calls that follow

[JocAnis]

Thanks hlev, but what is the meaning of big query? Maybe doing 'update' in for loop of online players?

If mp_chattime is working before server changelevel/plugin_end, that can help for some things

[hleV]

Yes, you'd be looping through all players and building the query string accordingly.

Something like this might work. Basically you'll build a single query for all the players in the server.

new bool:ChangingLevel = false;

public server_changelevel()
{
    ChangingLevel = true;

    // Big query
}

public client_disconnected(client)
{
    if (ChangingLevel)
        return;

    // Normal query
}

[klippy]

Originally Posted by JocAnis Problem isnt solved...i removed updating rows on mapchange, but present error is: Thread worker was unable to start

When does this error get thrown? At mapchange? Map start? First query? At any random point in time?

[JocAnis]

@klipica on mapchange that error was happening..but i guess adding bool to server_changelevel and checking it before sql_threadquery is fix for this (also see the idea about mp_chattime, i think it can help here)

@hlev thanks for the link, but i think doing bigger query in server_changelevel (30 players almost every time) cant be faster than executing plugin_end after server_changelevel, if you know what i mean :/

[hleV]

Originally Posted by JocAnis @hlev thanks for the link, but i think doing bigger query in server_changelevel (30 players almost every time) cant be faster than executing plugin_end after server_changelevel, if you know what i mean :/

One big query on mapchange should be more optimal than 30 queries (because client_disconnected() in your case will be called ~30 times before map changes).

[JocAnis]

yeah that is right
but i was reffering to other time intervals:

time of: server_changeleve to plugin_end()
time of: one_big_query to plugin_end()

just hoping server_changelevel is called after passing mp_chattime "seconds"

[hleV]

Can something happen between server_changelevel() and plugin_end() that you would want to save to the database? If so you can simply mark that map is changing, but do the big query on plugin_end().

new bool:ChangingLevel = false;

public server_changelevel()
{
    ChangingLevel = true;
}

public plugin_end()
{
    // Big query
}

public client_disconnected(client)
{
    if (ChangingLevel)
        return;

    // Normal query
}

[JocAnis]

im a little bad for iLen += format so i still cant make that big query

just more information about the problem:
plugin is being used in DeathrMatch FreeForAll (almost all the time 30/32 players)
so on that server query of UPDATE (kills for attacker and deaths for victim) are being sent every second or even faster, cuz killing are done every moment...so the problem is: duplicated rows in the table (i thought it was of nick characters) but im 90% it is 'slow' connection signal from cs server to mysql databases...so every query is being late for some moments, and before that one is finished, another one is sent and like that in loop...so at mapchange (even with bool at mapchange/server_changelevel) invalid handle is happening (already sent quries arent executed 100%)...

maybe changing to some 'faster' mysql database server is the solution...or that big query, but im not sure anymore :/

[hleV]

Then don't save on every kill/death. Just save on disconnect AND mapchange. This will only be a problem if server crashes, in which case latest data of connected players won't be saved.