Can MongoDB run effectively on an EC2 micro instance?

[Duke Dougal]

Hello

Amazon EC2 now has "micro instances" which are 64 bit instances with
minimal CPU and about 618 meg ram.

I logged in to one of them and it had about 400 meg RAM free after
loading Linux.

Is it practical to run MongoDB on such a machine? What sorts of
issues might come up with this small amount of RAM?

Thanks

as

[Kyle Banker]

You should be able to run modest applications on such an instance. As always, you want to keep indexes and working data set in RAM, so we'd expect to see these instances slow down as your data set grows and you have to go to disk more often.

So whether it's practical really depends on your app, data sizes, index size, access patterns, etc.

--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.

[mwaschkowski]

Hi Kyle,

Thanks very much for that info as I was hoping to run on a vps and
wasn't sure where I needed to start.

Whats the easiest way to monitor it so I can know when I need to bump
up the server with more resources?

ie. is there a server command that I can run and see when I'm getting
close to the limit?

Thanks a lot!

Mark

> > mongodb-user...@googlegroups.com<mongodb-user%2Bunsubscribe@google groups.com>
> > .

[Kyle Banker]

There are a lot of way to monitor. Probably the best is to keep an eye on performance. If the MongoDB log starts showing a lot of slow queries (i.e., > 100ms), then it's probably time to start upgrading.

You can check the % disk utilization:

iostat -x 2

Check the server status for index miss rate:

db.serverStatus();

And check index and data sizes:

db.stats();

To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.

[Igor Russkih]

Just for the information,

I had a staging vps with 64Mb (!) RAM - for test purposes mongo worked
fine for me, handling a couple of thousands documents, raw db data
size was about 1Gb.

Now I'm staging on VPS with 256Mb RAM.. Facing and tracking the
problems is quite straightforward - at some critical moment swapping
becomes huge and some queries start to consume alot of time.

On 15 сен, 19:37, Kyle Banker <k...@10gen.com> wrote:
> There are a lot of way to monitor. Probably the best is to keep an eye on
> performance. If the MongoDB log starts showing a lot of slow queries (i.e.,
>
> > 100ms), then it's probably time to start upgrading.
>
> You can check the % disk utilization:
>
> iostat -x 2
>
> Check the server status for index miss rate:
>
> db.serverStatus();
>
> And check index and data sizes:
>
> db.stats();
>

[mwaschkowski]

OK, thanks very much, very helpful.

Best,

Mark

On Sep 15, 11:37 am, Kyle Banker <k...@10gen.com> wrote:
> There are a lot of way to monitor. Probably the best is to keep an eye on
> performance. If the MongoDB log starts showing a lot of slow queries (i.e.,
>
> > 100ms), then it's probably time to start upgrading.
>
> You can check the % disk utilization:
>
> iostat -x 2
>
> Check the server status for index miss rate:
>
> db.serverStatus();
>
> And check index and data sizes:
>
> db.stats();
>