I just wanted to briefly explain why we are not planning on supporting local_db and recommending SXL instead. In the future the default will be to use SXL for everything.
Lets say you have a single user browsing foo.com and you are doing 10 HTTP requests a minute for that site, for 20 minutes. In CFF there is 200 lookups. In SXL there is 2 lookups. That is 1% of the lookups of CFF. In local db there are 0 lookups.
Lets say you have twenty users browsing foo.com, each doing 10 requests a minute for 20 minutes. In CFF there is 4,000 lookups. In SXL there is 2 lookups. That is .05% of the lookups of CFF. In local db there are 0 lookups.
So I agree that local db still has the least number of lookups. But SXL ain't that bad, and the more users the better the caching is. [:)]
I just wanted to briefly explain why we are not planning on supporting local_db and recommending SXL instead. In the future the default will be to use SXL for everything.
Lets say you have a single user browsing foo.com and you are doing 10 HTTP requests a minute for that site, for 20 minutes. In CFF there is 200 lookups. In SXL there is 2 lookups. That is 1% of the lookups of CFF. In local db there are 0 lookups.
Lets say you have twenty users browsing foo.com, each doing 10 requests a minute for 20 minutes. In CFF there is 4,000 lookups. In SXL there is 2 lookups. That is .05% of the lookups of CFF. In local db there are 0 lookups.
So I agree that local db still has the least number of lookups. But SXL ain't that bad, and the more users the better the caching is. [:)]
