So I'm building this web-site solution where high performance is a clear requirement. Pages content should not be static, but rather put together on the basis of supplied search criteria (basically tags); The page must include content for which associated tags match the supplied search criteria.
Since hearing about it, I've been planning on using a sqlite with the fts3 extension to "cache" data locally (on each web server (there will be several (and one main database))) in a form optimized for full-text- searching. Something like: _FTS3 Table_ Content Item|Tags "Some Entry"|"This is some tags" "Some other Entry"|"Some other set of of tags" As mentioned, it has to be fast (must support thousands of concurrent requests), but i am not not sure if sqlite is really appropriate for this. sqlite own docs says that it's only appropriate for medium ranged web-sites, but also as a replacement of ad-hoc data files (which this basically is); Also i've seen a post on in this group which talks about fts3 and hundreds-of-thousands of records. I'd appreciate any feedback you might have one this. Also, does anyone have experience with sqlite+ft3 and high-availability solutions? Has anyone done any benchmarking of fts3? - Jens _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
