), but it doesn't use binary searching... I tried using binary searching via Lists but it starts to slow everything down when you insert a new record into the index... i.e. resorting 50K records just grinds everything to a halt... JoSQL is useful in that it allows SQL statements to be applied to Lists of Java objects... I may implement indexes in JoSQL eventually... JoSQL is pretty quick though... It depends upon what your desired response time is...
For example on the following query:
WHERE name LIKE '%.html'
ORDER BY name
on 108K "FileWrapper" objects, the WHERE clause took:
~0.1s to execute
The ORDER BY part took:
~0.3s to execute for about 26K objects matched from the WHERE clause.
I executed the above query on my home machine running Liunx, 512MB ram, 2.4GHz processor...
You may be best off with a TreeMap... better insert performance, though can be slightly slower on searching...