04.04.2018, 13:57
I've been using DINI since 2009 for my vehicle ownership system however I'm starting to get serious about my server now and I know I need to optimise my script.
Now my question is, what'd be easier (I say easier because time is not something I have alot of), converting to a single-file system (ie still using dini but splitting lines) or converting to a database (mysql, sqlite)?
Currently I have one file per car, and these load as the vehicleid's on server-startup. Each command a player uses will save whatever has been modified on that car (components, colors, parking position etc) to the file of that vehicleid straight away. This works perfectly, but again, it's alot of files, and alot of reading & writing.
What'd be the pro's and con's, and would it actually be possible to convert a system rather than re-writing the whole thing? TIA.
Now my question is, what'd be easier (I say easier because time is not something I have alot of), converting to a single-file system (ie still using dini but splitting lines) or converting to a database (mysql, sqlite)?
Currently I have one file per car, and these load as the vehicleid's on server-startup. Each command a player uses will save whatever has been modified on that car (components, colors, parking position etc) to the file of that vehicleid straight away. This works perfectly, but again, it's alot of files, and alot of reading & writing.
What'd be the pro's and con's, and would it actually be possible to convert a system rather than re-writing the whole thing? TIA.