Filter by reset
- Everywhere
59 - Issues
17 - Pull Requests
1 - Comments
41
JSON performance degradation compared to SQL performance.
JSON performance degradation compared to SQL performance. CI github overnight test passed…results: • JSON: 117 ms and SQL: 108 ms The difference between…-sX POST http://localhost:9308/search -d '{"index" : "name", "query" : {"match…
discussion
Upgrade CLT version to the latest one
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
…order by id asc; This performance degradation is not expected and…/home/ilya/join_perf/data.sql Manticore Search Version: 6.3.9…
bugrel::7.4.6
Upgrade CLT version to the latest one
Write throughput degradation in 6.3.3
bug
…Checklist: You have searched for an answer in…3.1 for my search engine. I would…sql_host = localhost sql_user = [REDACTED] sql_pass = [REDACTED] sql_db = [REDACTED] sql_port = 3306 # sql…in the Manticore configuration. Performance Optimization: Optimize the…
waiting
done
Comparison of JSON overhead versus SQL overhead
…-sX POST http://localhost:9308/search -d '{"index" : "name", "query"…-sX POST http://localhost:9308/search -d '{"index" : "name", "query"…379s To check the performance metrics, you can do…-sX POST http://localhost:9308/search -d '{"index" : "name", "query"…
est::size_Mdone
Support client requests via NATS messaging system
Temporal adjustment for debugging perf
PR created based on issue https://github.com/manticoresoftware/manticoresearch/issues/2573 to find JSON performance degradation compared to SQL performance.
Sort_dict mem_limit is extrmely low
hi I am new to manticore and deploy one with k8s the version is 5.0.2 using a rt index which seems not require a static indexer configuration. here is my configmap as startup.sh #!/bin/sh set -e mkdir -p /var/lib/manticore/binlog hostName=${HOSTNAME} …
low priorityest::size_S
Add Support for multiple tables in the MATCH() Function for JOIN Queries
Proposal: Problem Description: In the current implementation, the MATCH() function used in JOIN queries only allows a single table to be specified. This limitation forces users to issue separate queries for each full-text search, complicating …
feature::join
Test performance for queries with multiple disk chunks
Is manticore multi threaded? saw c language inside also advisable to replace mysql as primary data store? any caveats / limitations? any performance benchmark against redisearch? what's the pro and cons of using manticore vs redisearch?
Test performance for queries with multiple disk chunks
Sorry for asking here, any slack or equivalent telegram chat channel?
Sorry for asking here, any slack or equivalent telegram chat channel? 1 question, possible to list the difference between manticore vs mysql and any benchmark for both? quite some time since i touched on manticore and now saw it as "DATABASE for search …
waitingwontfix
tests: fixed version issue in nightly tests
Currently mass inserts into a Manticore real-time table require batching for better performance. The task is to implement the INSERT DELAYED SQL command which would work as follows: INSERT DELAYED ... gets routed to Buddy Buddy saves the documents …
hacktoberfest
tests: fixed version issue in nightly tests
Incorrect query result when JOIN batching is enabled
…join_cache_size to improve performance | | total | 2 | | total_found | 2…/home/ilya/join_perf/data.sql Manticore Search Version: 6.3.9…
bugrel::7.4.6
tests: fixed version issue in nightly tests
…list to a paginated document search result, especially in corner cases…should be done before each search request. The problem is that…whole block list to an SQL query like WHERE id NOT…maintain and will affect FTS performance. Additional context In RDBMS it…
tests: fixed version issue in nightly tests
…of conditions and now found performance issues. maticore versio: 5.0….00 | | local_search | 0.000079 | 2 | 0.00 | | sql_parse | 0.000320…
waiting
tests: fixed version issue in nightly tests
…> select id, json.int from test1 order by json.int asc; +------+----------+ | id | json.int | +------+----------+ | 1 | 1 | | 11 | 1024 | | 8 | 128 | | 5 | 16 | | 15 | 16384 | | 2 | 2 | | 12 | 2048 | | 9 | 256 | | 6 | 32 | | 16 | 32768 | | 3 | 4 | | 13 | …
question
tests: fixed version issue in nightly tests
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 …
Test performance for queries with multiple disk chunks
FACET with json on engine columnar crash
Describe the bug FACET with json on engine columnar crash To Reproduce drop table test; CREATE TABLE test(pos text, ipaddress json) min_infix_len='1' engine='columnar'; insert into test(pos,ipaddress) VALUES('a','{ data: [\"127.0.0.1\",\"192.168.0.1\"] …
bug
fuzzy=1 extremely slow on OR query
bugwaiting
I started a seachd instance (3.5.2) using docker. searchd { listen = 9312 listen = 9308:http listen = 9306:mysql41 binlog_path = /var/lib/manticore pid_file = /var/run/manticore/serachd.pid data_dir = /var/lib/manticore watchdog = 0 preopen_indexes = 1 …
waiting
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
Test/update blocking by combining blocks
done