FullTextSearch/Examine CPU usage
# help-with-umbraco
s
Hello! We're using Lucene.Net v3.0.3 with Examine v1.2.2 in an umbraco v8.14.1 installation. We're also using https://github.com/skttl/umbraco-fulltextsearch8 package v1.3.0. Our externalindex has a document count of 8590 items with fieldcount of 109. We've exluded a lot of itemTypes and only have necessary document types added to the externalIndex. We've altered the externalindex by using this code: (look at customCode.cs file) In our backoffice we have a composition with a property 'allowSearching' that is added to each document type that should be in the externalIndex. As already mentioned, we're using the fulltextsearch package and we notice that our CPU is spiking when performing the nativeQuery code: return searcher.CreateQuery().NativeQuery(query.ToString()).Execute(_search.PageLength * _currentPage); Example of a query (look at query_1.txt file) This is an example where we would only search for one specific contentType. Another example is our 'findasyoutype' functionality that searches through some more contentTypes at once: (look at query_2.txt file) Any idea why the nativeQuery exeuction is causing high CPU usage of 100%? Any help would be greatly apreciated! Thanks! https://cdn.discordapp.com/attachments/1199273029579055124/1199273029855875153/query_1.txt?ex=65c1f10b&is=65af7c0b&hm=faae9457d3cc1f47974290d12f0174e9d4332f7d97be03c8dc16af799d8a858b& https://cdn.discordapp.com/attachments/1199273029579055124/1199273030149472256/query_2.txt?ex=65c1f10b&is=65af7c0b&hm=262d2d1ff2c5f62be1e92ec922cdb184a994db4dd00284c4e2cab89b1ee79d84& https://cdn.discordapp.com/attachments/1199273029579055124/1199273030464053329/customCode.cs?ex=65c1f10b&is=65af7c0b&hm=9777a3cf3737d1c3202c59b2602c895b414a40b3305ec5aec7614fad512c41af&
To add to this issue: Ive changed my code a bit and my queries now look like this:
+(FullTextContent_nl:ventilatie* FullTextContent:ventilatie* nodeName_nl:ventilatie* nodeName:ventilatie*) +(__NodeTypeAlias:contentpage __NodeTypeAlias:labitem __NodeTypeAlias:newsitem __NodeTypeAlias:project __NodeTypeAlias:technicalcommittee __NodeTypeAlias:standardsantennaitem __NodeTypeAlias:jobitem __NodeTypeAlias:tool __NodeTypeAlias:contact __NodeTypeAlias:technologiesdetail)
I've noticed that our CPU usage is also spiking when using this query in de examine management tab in our externalIndex to about 80-90%. anyone experienced this before?