Comments (6)
Hi, I discovered that I may have caused the problem by loading the thesaurus incorrectly. Currently I have about 50 items in it and when I comment out all but a few of them the CPU spiking goes away (and that fantastic Lifti-speed returns!). I will take a bit of time to figure out which item(s) are the culprit and get back to you.
from lifti.
Sorry!! I never was able to test it long enough to figure out why the slowdown occurred. I would like to get back to it.
Also, I didn't mention that we finally went to production with this and you have made some users extremely happy with 1 second search times compared to the 10 seconds that it was previously.
from lifti.
Are the queries that are being run the same? I would expect different operators to exhibit different cpu cost, so if the queries aren't identical then that could be part of it.
from lifti.
Assuming that what you're experiencing isn't a bug in LIFTI, the most likely cause will be due to an increased number of matches that need to be merged in the case of a query containing lots of search terms, or there is a wildcard in the query that's becoming computationally expensive to run.
Let me know what you find out - if there's a concrete example I can work with I'd be happy to find some time to take a look.
from lifti.
@markwriter I'm interested to know if you're able to share where you got to with this?
from lifti.
That's great to hear, @markwriter. I'll keep this issue open for a while in case you get chance to look into it any more.
from lifti.
Related Issues (20)
- Write up implementing a custom serializer
- Apply field and document filtering when collecting results from IndexNavigator HOT 1
- Add README.md to nuget package
- Provide a method to calculate the size of the index in memory
- Query syntax: Add support for spaces in field names HOT 6
- Query syntax: Support wildcard field searches/searching across all dynamic fields from a specific provider HOT 3
- Remove dependency on System.Collections.Immutable HOT 2
- Suggestion: custom stemmers HOT 2
- Search for words with a `=` character HOT 5
- Escaped characters in LIFTI query syntax HOT 1
- Q: is possible to fetch the whole document by Id? HOT 2
- Refresh documentation HOT 20
- Split IdPool and ItemStore HOT 1
- Consider switching to using ValueTask across the library HOT 1
- Operaterrors as a text HOT 3
- Standardize terminology
- Track source object type against a document's metadata
- Add a "not contains" query operator
- v6 documentation changes
- Create a standardised way of rehydrating an index from a serializer
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lifti.