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.

クエリタイプ	ヒット率	MySQL	MygramDB	高速化
超高頻度語	75%（128万件）	2,980ms	92ms	32倍
高頻度語	47%（80万件）	1,876ms	76ms	25倍
中頻度語	22%（37万件）	908ms	49ms	19倍

クエリタイプ	MySQL	MygramDB	高速化
超高頻度語	2,891ms	6.7ms	431倍
低頻度語	124ms	0.3ms	413倍

並列数	MySQL	MygramDB
10	9割失敗、QPS 0.4	全成功、QPS 288
100	実行不可	全成功、QPS 372

項目	MygramDB	Elasticsearch
導入	バイナリ1つ	クラスタ構築
データ同期	binlogで自動	ETLが必要
レイテンシ	80ms以下	50〜500ms
運用コスト	低い	高い
分散	なし	あり

ベンチマーク

検索性能（ORDER BY id LIMIT 100）

COUNT性能

並列性能

MySQL FULLTEXTが遅い理由

MygramDBが速い理由

Elasticsearchとの比較

ベンチマーク ​

検索性能（ORDER BY id LIMIT 100） ​

COUNT性能 ​

並列性能 ​

MySQL FULLTEXTが遅い理由 ​

MygramDBが速い理由 ​

Elasticsearchとの比較 ​