Better save system than nvault
Hello, does anyone know a better save system than nvault?
I have a problem with nVault that the bigger the db is the more lags are on my server, and after a week from server start (4k players passing by * 30 classes = 120 000 records) the server crashes and deletes half of the data (resets levels for players, or changes them, well it does weird stuff). I need a system that can handle a biig database without crashes or lags. I have mysql on localhost with the server but will that do better than nvault? Or maybe you know any better system? |
Re: Better save system than nvault
SQLite is another option
|
Re: Better save system than nvault
I wouldn't be a problem for MySQL do handle such a small amount of records for sure, unless you have wooden server.
...and make sure to use threaded queries. |
Re: Better save system than nvault
nVault is good because it's the easiest. Depending on the amount of data and the types of queries you need to make, SQL could be a better option. If you want to continue with nVault, is it possible to change how your data is being saved to less the number of entries per-player? Give an example of each players entries.
|
Re: Better save system than nvault
PHP Code:
I already use SQL and nVault together, SQL is for storing player's clans (1st table, uses IDs of players from the second one) and orders (money) + passwords (second table). Should I make another table for Player Class Data? It would make another 30 entries per each player. Would it be better optimized than nVault? The queries I make with nvault are: LoadData, SaveData and that's pretty much it. For SQL it's a lot more queries (1000+ per second?) because I use it in a function that is called each 0.1 second for EACH player (so if there are 32 players it is 32 queries per 0.1 second). I know it's not optimized and I'm working on a rewrite of this part. There are also queries made when someone says in chat like /clan, /account, /login, player connect, disconnect, synchronize data with SQL etc. I really don't know what save system would be best for that type of databases (I really work on them a lot). I think now I will work on pure SQL, but I have a question: Should I use SQL queries like I do now: PHP Code:
http://forums.alliedmods.net/showthread.php?t=227170 If you have any suggestions please post below |
Re: Better save system than nvault
to save player data, do it on client_disconnect and when round ends.
not do it in a forward that's called 0.1 seconds per each player on the server... |
Re: Better save system than nvault
Save player data (on nvault) is done on client_disconnect, load is done on client_connect.
I use SQL queries each 0.1 second (they are small ones, just one select, but I will change it so it will be executed like each 5 seconds). The problem is for sure with nVault, because I had the same problem in before, back then I didn't use SQL at all. Of course I'm talking about MySQL on LOCAL server. So, anyone can tell me if http://forums.alliedmods.net/showthread.php?t=227170 is better than using sqlx SQL_Connect and SQL_Execute? Because I'm rewriting my SQL code anyways and I need to find the most efficient functions. |
| All times are GMT -4. The time now is 23:20. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.