Live data from Hacker News

MongoDB 2.6 Released

blog.mongodb.org

91–100 of 119 posts

Re: MongoDB 2.6 Released

#91
post #31

Earlier quoted context omitted.

"Finally, MongoDB 2.6 lays the foundation for massive improvements to concurrency in MongoDB 2.8, including document-level locking." They hear you and are working on it.

It was about a year between the first release of 2.4 and the 2.6 release. Should we expect another full year for 2.8?

I believe they are on a ~yearly schedule now.

Re: MongoDB 2.6 Released

#92

A lot of hype... And we still have db level locking. If document level is too difficult, at LEAST do collection level (not that it is too much better, but least it some real improvement).

Heck I'd even be happy for them to do locking on a per file basis. (For those unfamiliar with mongodb, the actual database storage is broken up into 2GB files.)

I believe the 2 GB database limit is only applicable to 32-bit instances[0].

[0]: http://blog.mongodb.org/post/137788967/32-bit-limitations

Re: MongoDB 2.6 Released

#93

Earlier quoted context omitted.

Heck I'd even be happy for them to do locking on a per file basis. (For those unfamiliar with mongodb, the actual database storage is broken up into 2GB files.)

I believe the 2 GB database limit is only applicable to 32-bit instances[0]. [0]: http://blog.mongodb.org/post/137788967/32-bit-limitations

You are confusing two things. I am talking about the files making up a database. MongoDB doesn't use one file per database - instead it allocates files up to 2GB in size (the first one starts at 64MB and then they double in size until the 2GB limit). So for example a database that is 200GB will consist of (roughly) 100 2GB files.

What you linked to is a consequence of memory mapping. Mapping a single 2GB file in a 32 bit process will use up virtually all the address space and you couldn't map more than one at a time.

Re: MongoDB 2.6 Released

#94
post #85

I've been using Elasticsearch as a primary database for my new project, which has basically been a good NoSQL db that happens to have great search. However, peripheral tools(performance testing, hosting) have been a bit rough. How do the two databases compare now. Is search improving in Mongo or is that something they are not really worrying about at the moment.

if you are looking for a nosql dbms as a service which consumes json and supports SQL and search, you could try amisaserver

have you seen the pricing? it's insane

Re: MongoDB 2.6 Released

#95
post #85

Earlier quoted context omitted.

if you are looking for a nosql dbms as a service which consumes json and supports SQL and search, you could try amisaserver

have you seen the pricing? it's insane

The price is unbelievably fair. Try deploying mysql in the cloud and while you are at it, you get Redis as well for cache and then you hit the wall you need search in your application, so you deploy elastic search as a service as well. Do the math and compare to ours.

Our pricing starts as low as $15 per month

The cheapest instance of amazon cloudsearch is around $79 monthly, You then have to deploy a transactional DBMS and then most likely S3 for storage as well.

Re: MongoDB 2.6 Released

#96

Earlier quoted context omitted.

have you seen the pricing? it's insane

The price is unbelievably fair. Try deploying mysql in the cloud and while you are at it, you get Redis as well for cache and then you hit the wall you need search in your application, so you deploy elastic search as a service as well. Do the math and compare to ours. Our pricing starts as low as $15 per month The cheapest instance of amazon cloudsearch is around $79 monthly, You then have to deploy a transactional D…

It's 700/month (otherwise your product isn't needed because no-sharding? postgresql can do most of the stuff)

the hosted version is upto 8gb ram, don't you think that's low ?

sqlserver + oracle are also insane

Re: MongoDB 2.6 Released

#97

Earlier quoted context omitted.

The price is unbelievably fair. Try deploying mysql in the cloud and while you are at it, you get Redis as well for cache and then you hit the wall you need search in your application, so you deploy elastic search as a service as well. Do the math and compare to ours. Our pricing starts as low as $15 per month The cheapest instance of amazon cloudsearch is around $79 monthly, You then have to deploy a transactional D…

It's 700/month (otherwise your product isn't needed because no-sharding? postgresql can do most of the stuff) the hosted version is upto 8gb ram, don't you think that's low ? sqlserver + oracle are also insane

$700 annually. Please read well before you misrepresent us.

By the way Partitioning by Hash and Range as we have stated means "Sharding"

Re: MongoDB 2.6 Released

#98
post #35

Earlier quoted context omitted.

Am glad someone has brought up TokuMX. Tell me, have you used it in production yet? I wonder why 10gen hasn't made any official comment on the work the folks at Tokutek are doing to enhance Mongodb's features.

> I wonder why 10gen hasn't made any official comment on the work the folks at Tokutek are doing to enhance Mongodb's features. Why would they comment? What would they say? Toku is basically trying to steal MongoDB's customers, they even use the same basic pricing model.

For me the really irritating thing is the observation that when I want to enjoy flame wars about Mongo, I seem to see a lot of their 'try TokuMX' everywhere. Last time I checked they are on the 2.2 codebase, unless that recently changed. Mongo 2.4 was a significant upgrade, and assuming I'm correct above, I feel like the Tokutek team disregard that. I get that it's good marketing to suggest an alternative, but going along criticising that which you've built upon doesn't go well with me.

Re: MongoDB 2.6 Released

#99

Earlier quoted context omitted.

High volume of writes

High volume of writes from MANY producers. From 1 producer, it doesn't matter. Though the point of mongo is to be webscale which implies to me many writers.

In my experience, even 1 producer caused a full database lock for hours on our production server. We have 1 mongo server and an erroneous scheduled task of ours started at about 6am. It's only one process but the task basically re-syncs an entire collection (which was about 80,000 writes).

That single producer caused wide-scale locking/hanging for all readers on the website and I had to manually stop the task during business hours because of that. Oy!

Re: MongoDB 2.6 Released

#100
post #98
post #35

Earlier quoted context omitted.

> I wonder why 10gen hasn't made any official comment on the work the folks at Tokutek are doing to enhance Mongodb's features. Why would they comment? What would they say? Toku is basically trying to steal MongoDB's customers, they even use the same basic pricing model.

For me the really irritating thing is the observation that when I want to enjoy flame wars about Mongo, I seem to see a lot of their 'try TokuMX' everywhere. Last time I checked they are on the 2.2 codebase, unless that recently changed. Mongo 2.4 was a significant upgrade, and assuming I'm correct above, I feel like the Tokutek team disregard that. I get that it's good marketing to suggest an alternative, but going…

Last time you checked was a while ago, it's 2.4 compatible now (except geo and full-text) and has been since TokuMX 1.3.

We generally don't criticize indiscriminately. MongoDB has a lot of good sides and we embrace and extend those, and where it has faults we try to work around or replace them. Our core strength is fast, reliable, compressed storage and MVCC semantics, so obviously we talk about that a lot, but we also understand and acknowledge that a large amount of TokuMX's success, to the degree it has some, is due to the excellent parts of MongoDB.

As an example, I personally am really excited about what MongoDB has done with aggregations in 2.6 (and what seems to be coming down the pipe soon), and I can't wait to merge it in to TokuMX. We all get stronger together.

Post reply on HN