Sqlite vs mysql,which will cause high I/O

[thewayur]

So, i guess mysql queries do not count under I/O,
but sqlite will be for sure? right?

(cant ignore max file size =10mb)

well, can someone please ensure response time of mysql? cause i will have to recreate db.

[Admin]

The IO usage of accounts is tracked through the storage interaction of your PHP code. So a PHP script writing a SQLite database on your account does generate IO usage, but MySQL does not.

MySQL in general is also faster than SQLite, and can handle a lot more data and traffic without issues. We also balance system load differently on the database servers as they are more sensitive to high CPU usage.

Overall, using MySQL will improve the performance of your site while reducing most account usage metrics.

[thewayur]

Yes, thanks for clarification.

but as sqlite is totally offline and local db, it is 2x 3x times faster, where as mysql makes a server request there is a response delay.

so u mentioned: So a PHP script writing a SQLite database on your account does generate IO usage,
it means any R/W with sqlite db will cause I/O.

right dear Admin?

Overall, using MySQL will improve the performance of your site while reducing most account usage metrics.
well it depends on app’s need, concurrent clients and management.
AFAIK, for a single/few clients interaction. sqlite is best.

[Admin]

@thewayur

so u mentioned: So a PHP script writing a SQLite database on your account does generate IO usage,
it means any R/W with sqlite db will cause I/O.

right dear Admin?

The writes are most relevant, but yes, this is true.

@thewayur

Overall, using MySQL will improve the performance of your site while reducing most account usage metrics.
well it depends on app’s need, concurrent clients and management.
AFAIK, for a single/few clients interaction. sqlite is best.

On a small site with very little users, SQLite may be a bit better than MySQL. But as the amount of data grows, a dedicated database program can access, load and cache data much more efficiently than SQLite, which far outweighs the <1ms latency to a remote database server. And with more concurrent users, SQLite’s extremely simple locking mechanism will cause problems.

And moving from SQLite to MySQL later on is quite painful as you can’t easily take an export from one program and just load it into the other system.

So unless you’re 100% sure that your project will never get more than a little bit of data and a few users, going with MySQL from the start will make it easier to grow your site later on.