Performance considerations about flintstone

[hypeJunction]

I did see it, and it does look great. My plugin integrates with a larger framework that already has a memcached wrapper, so it was easy to write my own adapter.

[fire015]

Great question! Reading from memory is always going to be faster than reading from disk. I haven't benchmarked it to that scale but I would say choosing something like memcached/redis is a better option if you are having hundreds of reads per page. However it is a trade off - using something like memcached comes with more maintenance from a devops point of view. It's also not a permanent memory store so you would need a fallback like a database if the data does not exist. Totally depends on your use case and how willing you are to optimise your site for speed. I hope that helps :)

[hypeJunction]

I do have a database table, which contains additional information about each route. I needed a fast way to rewrite all inline URLs on the page without having to query the database to get the target path.
I have integrated memcached today and left flintstone in as a fallback for servers that are not memcached. There was a considerable improvement in speed.

[fire015]

Great. There is a nice package written by @adammbalogh which allows you switch out flintstone for memcached/redis without any code changes, would recommend you take a look: https://github.com/adammbalogh/key-value-store