Filter by reset
- Everywhere
9113 - Issues
2118 - Pull Requests
1012 - Comments
5983
Adjusting the regular expression to calculate performance.
done
Optimize performance of REPLACE INTO SET
Proposal: # manticore-load \ --drop \ --batch-size=1000 \ --threads=5 \ --total=1000000 \ --init="CREATE TABLE test(id bigint, name text, type int)" \ --load="INSERT INTO test(id,name,type) VALUES(<increment>,'<text/10/100>',<int/1/100>)" # rm /tmp/sql; …
waitingest::size_S
❓ Per-field tokenization (question for the community) ❓
Queries are slow, about 200 million data points.
This is my configuration, version 3.4.2 runs in docker.CPU 2 core, memory 2G. searchd { listen = 9312 listen = 9308:http listen = 9306:mysql41 log = /var/log/manticore/searchd.log query_log = /var/lib/manticore/data/query.log binlog_path = /var/lib/ …
waitingwontfix
how to search fast with ramchunk(rt table) in High-Frequency Write Systems
rel::7.0.0
Test Profile-Guided Optimization (PGO)
I forked benchmarks to https://github.com/abhijo89-uc/benchmarks/ and updated from plain index to rt index. then perform the same test . Its really slow !! Any comments ? Google sheet is : https://docs.google.com/spreadsheets/d/ …
Performance degradation in b632b/709b9
There are several performance degradations in 20230909 b632b 709b9 (compared to 20230624 75a47 35b04 ). One of them is because I limited maximum threads in all fulltext queries to the number of physical cores. My benchmarks show that most of the time …
est::size_M
how to search fast with ramchunk(rt table) in High-Frequency Write Systems
rel::7.0.0
Related to #1103
Feature Request: Different Data Formats
Test Profile-Guided Optimization (PGO)
Is your feature request related to a problem? Please describe. Not a problem - just an idea of how to (possibly) improve ManticoreSearch performance. Describe the solution you'd like Recently I did a lot of testing Profile-Guided Optimization (PGO) on …
waiting
Implemented performance optimizations for join batching
Implemented performance optimizations for join batching
6.2.0 gives syntax error, older versions don't
bugest::NO_ESTIMATErel::6.3.0
Implement batching inside a join query
Proposal: Currently join works by generating a query to the right table for every match in the left table and storing the result in a cache. If there are a lot of unique join conditions, this is very slow. We could accumulate join conditions for several …
rel::7.0.0
est::size_S
I have an index with 200 full text fields in it. I prepared 3.8 million data, but the data is highly repetitive. It takes 250-300 milliseconds on average to run the following query. create table test (e, s0.....s199) rt_mem_limit='1024m' min_prefix_len = …
Histograms are slow when estimating large IN(...) filters
bugrel::7.4.6
What are the factors that affect search efficiency?
Want to consult, have those factors to affect search efficiency. Because I've learned from elasticSearch that an index should not be too much larger than available memory, so response times are millisecond level. Does manticore have the same mechanism? …
discussion
bugrel::7.4.6
how to search fast with ramchunk(rt table) in High-Frequency Write Systems
Confirmation Checklist: You have searched for an answer in the manual. You have considered using the forum for general discussions, which can be more suitable for non-urgent or broad queries. You are aware of our community support channels on Slack, …
rel::7.0.0
how to search fast with ramchunk(rt table) in High-Frequency Write Systems
rel::7.0.0
Manticore 4.0.2 slower than Manticore 3.6.3
…Hi, I have a production 3.6.3 installation and I'm evaluating to migrate to 4.0.2, before this upgrade I'm doing some stressing tests to evaluating performances. Here the steps to compare the results: I started a VM Centos 7 with Manticore 3.6.3 …
Slow performance SNIPPETS on agent index
bugwaiting
Queries on taxi dataset are slow with ps=1
Queries on partial taxi dataset (6 indexes) are almost 2x slower with pseudo_sharding enabled: mysql> set global pseudo_sharding=0; SELECT avg(total_amount) FROM taxi WHERE trip_distance = 5; show meta; Query OK, 0 rows affected (0.00 sec) …
bugrel::6.2.0
Is there a way to apply morphology to the data field in CALL PQ?
bug
optimize grouping by time further
A query like this is now about 10 times faster than before revamp of the date/time functions, but as discussed there still seems to be room for further optimization: mysql> SELECT year(pickup_datetime) as y, count(*) trips FROM taxi GROUP BY y ORDER BY y …
est::NO_ESTIMATE
Manticore 4.0.2 slower than Manticore 3.6.3
select ... join + facet against 2 tables of 277562 and 8671 docs is too slow: snikolaev@dev2:~$ mysql -P9306 -h0 Server version: 6.2.13 8db8be098@24031215 dev (columnar 2.2.5 aa3504b@240304) (secondary 2.2.5 aa3504b@240304) (knn 2.2.5 aa3504b@240304) git …
est::size_Mfeature::join
performance degradation with wildcard queries with many matches when disk_chunks > 1
Bug Description: There is a noticeable decrease in the speed of executing wildcard queries with an index using two or more disk chunks compared to the speed of executing the same queries with the same data using one disk chunk. This issue was not observed …
bugrel::6.3.4
agent_retry_count does not work with ha_strategy nodeads and noerrors
Is it possible to limit the memory usage of the searchd process
I find that after batch insert data to manticore, the usage of the searchd process not free the memory? This is my config file index hacker_new { type = rt rt_mem_limit = 2048M path = /home/mcsearch/index/hacker_new rt_attr_bigint = story_id rt_attr_ …
waiting
bugwaiting
fuzzy=1 extremely slow on OR query
Bug Description: Using fuzzy=1 this OR query is extremely slow. this is a basic query. If I add all select+where fields the query runs at least 20+seconds with fuzzy=1 and without in 50ms! SELECT field FROM index WHERE MATCH('php | (^php$)') 16ms SELECT …
bugwaiting
Optimize performance of REPLACE INTO SET
waitingest::size_S
