Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

alisql 与 oceanbase的区别，该如何选择？ #37

Open
cosdy opened this issue Jan 18, 2017 · 1 comment
Open

alisql 与 oceanbase的区别，该如何选择？ #37

cosdy opened this issue Jan 18, 2017 · 1 comment

Comments

@cosdy
Copy link

cosdy commented Jan 18, 2017 •
edited
Loading

大数据，高并发(比如：10wQps，单表千亿条记录)，且不想分库分表，该选择哪一个？
@xpchild
Copy link
Contributor

xpchild commented Jan 19, 2017

物理极限决定了单机很难支持这么高的吞吐能力了， 需要分布式数据库来scale， 我们提供了petadata这样的分布式数据库， 您可以对比下oceanbase和petadata，在分库分表功能对用户的透明度，分布式环境下的功能tradeoff（比如join，事务等），来做一个对比，选择一个适合自己业务的。

lehoon pushed a commit to lehoon/AliSQL that referenced this issue Mar 1, 2017
[feature] Issue alibaba#37: Support MTS distributing in table level
945e59d 
MySQL 5.6 introduce Multi-Threaded Slaves(MTS) which significantly improved
replicating capability of slave. However, the original MTS only support
distributing in schema level, which limits the parallelism of worker threads.

For example, if all updates on master is under one schema, there will be
only one worker applying events, and degenerate to signle thread replication.

To solve this problem, we add a new distributing level, table mode.
In the new mode, events can be distributing to different workers as long as
different tables is involed.

A new global option "slave_pr_mode" is introduced, which can be configured as:
1. schema, distributing in schema mode, same as origial;
2. table, distributing in table mode.

Note: if changed dynamically, please remember to restart SQL thread,
i.e. "stop slave sql_thread; start slave sql_thread", to make the changes
take effect.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cosdy @xpchild