Quote:
Originally Posted by Potato Uno
This is an sqlite database, so each query takes microseconds (~ 0 ms) to execute.
|
There are far most costs involved with a sqlite query than just the execution time as seen from a plugin. You'll have a massive disk I/O hit when sqlite decides to flush the database to disk. If you use transactions you'll see an additional hit from journalling. Depending on the kind of disk you're running on, this can bring SRCDS to a halt if it attempts to read/write a file when your I/O queue is growing.
Food for thought: properly tuned
mysql servers can handle thousands of queries per second. Your bottleneck won't be the database, it will be how quickly SM's database worker thread can handle your query throughput. For that, you'll have to do some profiling, but 15 queries a second sounds like such a minuscule amount.
__________________