Skip to content

Freeze table map event #97

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.

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

Merged
merged 2 commits into from
Oct 21, 2014
Merged

Freeze table map event #97

merged 2 commits into from
Oct 21, 2014

Conversation

julien-duponchelle
Copy link
Owner

By not supporting alter table we can get huge performance gains.
The reason is we can skip parsing TableMapEvent

It's an optional parameter.

By not supporting alter table we can get huge performance gains.
The reason is we can skip parsing TableMapEvent

It's an optionnal option
@bjoernhaeuser
Copy link
Collaborator

What's the problem with ALTER TABLE? Still 👍 if it speed's up things :)

@julien-duponchelle
Copy link
Owner Author

If you want to support ALTER TABLE you need to parse all TableMapEvent in
case of a change in the table. This operation is costly and you have a
TableMapEvent each time a query hit a different table.

2014-10-11 14:31 GMT+02:00 Björn Häuser [email protected]:

What's the problem with ALTER TABLE? Still [image: 👍] if it speed's up
things :)

Reply to this email directly or view it on GitHub
#97 (comment)
.

julien-duponchelle added a commit that referenced this pull request Oct 21, 2014
@julien-duponchelle julien-duponchelle merged commit 3621149 into master Oct 21, 2014
@julien-duponchelle julien-duponchelle deleted the freeze_table_map_event branch October 21, 2014 08:11
@julien-duponchelle julien-duponchelle restored the freeze_table_map_event branch May 10, 2015 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants