You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original launchy could search this in less than a second, it takes this version 10 seconds to find the word disk. about 3 seconds to echo the d.
I am running on an Intel I7-4960X Extreme CPU (over clocked to 4GHz) with 64GB of DDR3 memory. This is a powerful CPU so I don't think I'm CPU bound.
Since you are building an index rather than just searching the directory paths you could build some kind of data base structure like R-Tree, or keep the index sorted and do a binary search.
The text was updated successfully, but these errors were encountered:
I have >42,250 items in the index and it runs absolutely light speed for me.
Can you determine whether it's related to the number of items in the index, perhaps by reducing the search depth, or removing a line from the catalogue directory list.
I have 723756 items in the index.
The original launchy could search this in less than a second, it takes this version 10 seconds to find the word disk. about 3 seconds to echo the d.
I am running on an Intel I7-4960X Extreme CPU (over clocked to 4GHz) with 64GB of DDR3 memory. This is a powerful CPU so I don't think I'm CPU bound.
Since you are building an index rather than just searching the directory paths you could build some kind of data base structure like R-Tree, or keep the index sorted and do a binary search.
The text was updated successfully, but these errors were encountered: