3 ms·
Most have some sort of caching logic but you can't rely on it to do what you want. Always benchmark, and never assume that just because you're paying for somet
by nostrademons 11y ago
Most have some sort of caching logic but you can't rely on it to do what you want. Always benchmark, and never assume that just because you're paying for something or that it's the industry standard, it does what you want. I've seen a number of devs completely surprised by the throughput & latency numbers they get from their databases because they assume everything is going to be cached in RAM and the database is really hitting disk for some obscure reason on every query.
- amelius 11y agoThis is all really hypothetical. Show me a DB that can do tries first.
- tokenrove 11y agoPostgres with SP-GiST, for example
- jessaustin 11y agoYou're the one insisting that this technique has to involve a database. It really doesn't!
- mdellabitta 11y agohttp://lucene.apache.org/solr/ http://lucene.apache.org/solr/
- batbomb 11y agoUsually this is due to dev ignorance of the five-minute rule and/or a failure to properly account for size of data. That being said, it really depends on the problem at hand and the overall workload of the database.