Question 1

Why is MySQL FULLTEXT so slow?

Accepted Answer

MySQL FULLTEXT is slow because it stores indexes on disk using B-tree pages, requires disk I/O for every query, uses uncompressed posting lists, and suffers from cache dependency. Under concurrent load, 90% of queries fail at just 10 connections. MygramDB solves this with in-memory indexing delivering consistent sub-80ms latency.

Question 2

How does MygramDB sync with MySQL?

Accepted Answer

MygramDB uses GTID-based binlog replication to sync with MySQL in real-time. It acts as a MySQL replica, receiving changes via the binary log. No ETL pipelines or manual sync needed. Write to MySQL as usual, MygramDB updates automatically.

Question 3

How much faster is MygramDB than MySQL FULLTEXT?

Accepted Answer

MygramDB is 27-3700x faster than MySQL FULLTEXT. For typical ORDER BY id LIMIT 100 queries, it achieves 19-32x speedup. COUNT queries are 413-431x faster. Under 10 concurrent queries, MySQL fails 90% while MygramDB achieves 288 QPS with 100% success rate.

Question 4

Does MygramDB support Japanese/Chinese/Korean text?

Accepted Answer

Yes, MygramDB has excellent CJK support using ICU-based Unicode normalization and N-gram tokenization. It handles Japanese, Chinese, and Korean text perfectly without additional plugins or configuration.

Question 5

What is the difference between MygramDB and Elasticsearch?

Accepted Answer

MygramDB is a single-binary deployment with direct MySQL binlog sync, sub-80ms latency, and low operational complexity. Elasticsearch offers distributed search and advanced features but requires cluster management, ETL pipelines, and JVM tuning. Choose MygramDB for simpler MySQL-based applications; Elasticsearch for large-scale distributed search.

Query Type	Match Rate	MySQL	MygramDB	Speedup
Ultra high-freq	75% (1.28M rows)	2,980ms	92ms	32x
High-freq	47% (807K rows)	1,876ms	76ms	25x
Medium-freq	22% (375K rows)	908ms	49ms	19x

Query Type	MySQL	MygramDB	Speedup
Ultra high-freq	2,891ms	6.7ms	431x
Low-freq	124ms	0.3ms	413x

Load	MySQL	MygramDB
10 concurrent	90% failed, QPS 0.4	100% success, QPS 288
100 concurrent	Cannot execute	100% success, QPS 372

	MygramDB	Elasticsearch
Deployment	Single binary	Cluster setup
Data sync	Direct MySQL binlog	ETL required
Latency	Sub-80ms	Higher
Complexity	Low	High
Distributed	No	Yes

Benchmarks

Query Performance (ORDER BY id LIMIT 100)

COUNT Performance

Concurrent Performance

Why MySQL FULLTEXT is Slow

Why MygramDB is Fast

vs Elasticsearch

Benchmarks ​

Query Performance (ORDER BY id LIMIT 100) ​

COUNT Performance ​

Concurrent Performance ​

Why MySQL FULLTEXT is Slow ​

Why MygramDB is Fast ​

vs Elasticsearch ​