[SkyFlare]

Quote:

Originally Posted by Variable™ Are you experiencing performance trouble doing it this way? I'd say that having tables for each system separately and updating them when needed is a better idea, and is safer when it comes to facing errors, since one system or two would get affected, not the entire saving system. I'd say, lesser queries = lesser requests and may slightly be better on your performance but you should consider maintaining well-structured queries when you are considering performance, keeping queries organized according to what they are being used for is better in my opinion. I see some people consider using one big query is better but since you're using pawn in your case, you need to create a very big string if you want to use one query, and you will eventually need to split up this query so it wouldn't do a difference any more, you will mostly end up doing it how you do it now. Except that you will waste time and effort. I always recommend having stuff organized, and sometimes it might not be the best for performance, but it's worth it.

Thanks for the detailed response, I am not seeing any Performance issues right now, I just feel like how it's handling it right now, OnPlayerDisconnect, its saving all that data, regardless if its split up into different queries like ive done or not, if I was to split the systems up, id still be saving it all, I just am worried if this was to be used on a larger scale of like 200+ players, the disconnects being so frequent, it may make my server hang, thats my worry at the moment, I basically am seeing if the way I am doing it now, is the most efficient available, or is there a tweak I can do, to prevent having to save ALL the data on exit? I mean if I make sure I am saving the data in all areas when its changing, id not need to on disconnect right?