1. No network round trips
2. SQLite runs in the same process as your app, so reading from SQLite is basically like calling a function in your program (from a performance point of view).
I checked the benchmarks page [0], they run the Redis in same machine. And also, running Redis in different machine and connecting over networking isn't same compared to using diskcache.
SQLite runs in the same process as your app, so reading from SQLite is basically like calling a function in your program
But SQLlite needs to write to disk, which will be much costly.
Comments
I would say:
1. No network round trips 2. SQLite runs in the same process as your app, so reading from SQLite is basically like calling a function in your program (from a performance point of view).
I checked the benchmarks page [0], they run the Redis in same machine. And also, running Redis in different machine and connecting over networking isn't same compared to using diskcache.
But SQLlite needs to write to disk, which will be much costly.
[0] - http://www.grantjenks.com/docs/diskcache/cache-benchmarks.ht...