1. Reneb submitted a new resource:

    Player Database - big database with light weight way to save it to prevent lags

    Read more about this resource...
     
  2. Hi! Right Now when i start my new fresh server is safe to install this? or is in test mode?!
     
  3. yes you can install it. At the moment it will only record player names and steamids
     
  4. Reneb updated Player Database with a new update entry:

    1.0.1

     
  5. Why not SQLite?
     
  6. same problem as the rest it saves on every change of the database that is not good for high amount of info
     
  7. Reneb updated Player Database with a new update entry:

    1.0.2

     
  8. But what if a server is crashed? Then data will not be saved because you save it only on unload and server save. I think...
     
  9. yes that is true deer_swag
    but on the server i manage with high pop, the server drops to 5fps with all the plugins: playernames, uniquename, etc
    that save on everychange
    unloading those plugins gave me back 120fps
    and this plugin doesnt cause those lags.
    [DOUBLEPOST=1442747935][/DOUBLEPOST]+ it doesn't really matter, if the server crashs, the server will rollback, so it doesn't matter if the plugin rollback to the exact same moment
    [DOUBLEPOST=1442748056][/DOUBLEPOST]and i know i asked you to update your plugin, but i thought that making 5 plugins that call things on playerinit to the same plugin, wouldn't be optimized, so i decided to put max informations in this plugin (just didnt have time to add more)
     
  10. Hmmm... I have thought that you can make an API. For example my plugins can add data to queue in your plugin and then (put aside unload/onsave) on timer it will save all data to one file. Or when amount of messages in queue greater than amount of connected plugins. Something like that.
    [DOUBLEPOST=1442752920][/DOUBLEPOST]Oh. I understood your last message. I don't know. Generally I think that SQLite or MySql will be faster than json anyways.
     
  11. mysql: blocks the server until the request is sent, so good if it's local, very bad if it's not
    sqlite: saves on everychange, so even if it's faster then json, it's still horrible for high amount of data.
     
  12. When I used sqlite on another game I used to build query strings instead of actually executing them, then execute them at a point you choose (being whatever is the fastest scenario)
     
  13. Reneb updated Player Database with a new update entry:

    1.0.3

     
  14. Pretty sure the MySQL extension was updated to work async so it shouldn't lock up the server anymore.
     
  15. oh so this is interesting!
     
  16. Reneb updated Player Database with a new update entry:

    1.0.4

     
  17. Reneb updated Player Database with a new update entry:

    1.0.5

     
  18. Why you don't use SQLite ???
     
  19. Wulf

    Wulf Community Admin

    SQLite isn't necessarily better.
     
  20. Isn't it really better for big data storage?