We've already optimized Backdrop to the point that a database connection is not necessary if you're using an alternative cache-backend like Memcache. Even though the database is unnecessary except for the single query to get the cached page, we still need that database connection just for that single query.
I was experimenting with using a flat-file cache as an alternative, a basic port of https://www.drupal.org/project/filecache. The results were fairly promising running ab -c 100 -n 100 http://backdrop.local/:
Database cache:
Requests per second: 569.45 [#/sec] (mean)
Time per request: 175.608 [ms] (mean)
Time per request: 1.756 [ms] (mean, across all concurrent requests)
Transfer rate: 12078.02 [Kbytes/sec] received
File cache:
Requests per second: 741.53 [#/sec] (mean)
Time per request: 134.857 [ms] (mean)
Time per request: 1.349 [ms] (mean, across all concurrent requests)
Transfer rate: 15727.74 [Kbytes/sec] received
So roughly a 30% performance increase in cached page delivery. The downside is that the disk becomes littered with non-sense cache files. But as far as disk-space goes, this is no different from the page cache, which takes up just as much room, but it's hidden away in the database.
If we can test this approach on various servers and consistently get a similar increase, I think we might consider bundling a flat-file cache and using it by default for the page cache.
Recent comments
RE: duplicate files —If an image is disassociated from any content, the system will delete it after x number of hours. (Six, I believe.)
Problem with Field image • Select existing file
For now, I’ve switched to the Seven theme. It’s a very good theme, too. Finally, "select existing file" is important. Otherwise, you end up loading tons of unnecessary, duplicate...
Problem with Field image • Select existing file
Oh, thank you! I have also been frustrated with this, but haven't tried since switching from Gin theme.
Problem with Field image • Select existing file