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

Creating many tables eats memory #1644

Open
danielmewes opened this issue Nov 13, 2013 · 2 comments
Open

Creating many tables eats memory #1644

danielmewes opened this issue Nov 13, 2013 · 2 comments
Labels
tp:performance
Milestone
backlog

Comments

@danielmewes
Copy link
Member

I had a 4 node cluster on EC2, with m1.medium instances. Each such instance has 3.75 GB of memory.
I created 200 (empty) tables and one of the RethinkDB servers got killed by the OOM handler.

Something there is using more memory than I would expect.
I didn't insert any data, nor ran any other queries apart from table_create. I did use the web interface though to watch the cluster's status.
@danielmewes danielmewes mentioned this issue Aug 20, 2014
Closed
@danielmewes
Copy link
Member Author

The current state of this is that each table uses about 8 MB of memory when its empty.

@danielmewes danielmewes mentioned this issue Aug 27, 2014
Closed
@timmaxw timmaxw mentioned this issue Nov 17, 2014
Closed
@danielmewes danielmewes mentioned this issue Mar 18, 2015
Closed
@danielmewes danielmewes modified the milestones: backlog, subsequent Mar 24, 2016
@oliverjanik
Copy link

Is there anything that can be done about this? What is in the overhead?

This was referenced Nov 18, 2020
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
tp:performance
Projects
None yet
Milestone
backlog
Development

No branches or pull requests
3 participants
@coffeemug @danielmewes @oliverjanik