News for hackers. Stuff that matters.
Re:MongoDB 1.4 Production Release by aaronbrethorst on Thursday March 25, 2010 @02:49PM (#1219135)
I am incredibly excited about the inclusion of geospatial indexing and searching (http://www.mongodb.org/display/DOCS/Geospatial+Indexing), especially with the impending release of full-text search next quarter (http://jira.mongodb.org/browse/SERVER-380).
Re:MongoDB 1.4 Production Release by pibefision on Thursday March 25, 2010 @03:04PM (#1219190)
full-text search would be amazing.
Re:MongoDB 1.4 Production Release by mark_l_watson on Thursday March 25, 2010 @04:01PM (#1219341)
I wrote about how easy it is to do some form of index and search: http://markwatson.com/blog/2009/11/mongodb-has-good-support-...
Re:MongoDB 1.4 Production Release by thibaut_barrere on Thursday March 25, 2010 @06:59PM (#1219786)
Same here - I've been using Sphinx quite a lot for geospatial stuff before. This feature was the only reason why I was still using it instead of MongoDB for some projects.

I'm already gone :)

Re:MongoDB 1.4 Production Release by pibefision on Thursday March 25, 2010 @02:02PM (#1219013)
Just a question: mongo uses some kind of memory cache like memcached? or I need to implement it aside to get faster-faster performance? I'm thinking on a small app (10K visitors a day).
Re:MongoDB 1.4 Production Release by javery on Thursday March 25, 2010 @02:03PM (#1219016)
Mongo should be fast enough that you don't need to use memcached. It uses memory mapped files (which is also important to know since by default it only flushes data to disk every 60 seconds)
Re:MongoDB 1.4 Production Release by antirez on Thursday March 25, 2010 @02:11PM (#1219038)
Memory mapped files are nice, but once the mapped file starts to get much bigger than the physical memory pages the operating system can allocate, it starts to be asymptotically the same as accessing the filesystem from the point of view of latency, so indeed for datasets considerably bigger than RAM it is not possible to be as fast as memcached. Not a MongoDB limit, but a nature-imposed limit :)
Re:MongoDB 1.4 Production Release by amix on Thursday March 25, 2010 @02:26PM (#1219063)
I have had some bad experiences with memory mapped databases (particularly Berkeley DB and Tokyo Tyrant) - both these seem to be very greedy with IO writes when one starts to have lots of data and lots of updates. I think Reddit experienced a similar problem (as memcachedb is based on Berkeley DB).

Does anybody know what Cassandra does?

Re:MongoDB 1.4 Production Release by uggedal on Friday March 26, 2010 @05:22AM (#1220601)
Re:MongoDB 1.4 Production Release by dm_mongodb on Thursday March 25, 2010 @02:29PM (#1219070)
this blog post talks a bit about a real world implementation and when they do and do not use memcached with mongodb: http://www.businessinsider.com/how-we-use-mongodb-2009-11
Re:MongoDB 1.4 Production Release by ccarpenterg on Thursday March 25, 2010 @03:16PM (#1219229)
I've tried MongoDB with the C++ API. I had a lot of problems in particular with the BSON objects and then switched to Memcached (+ MySQL). Do you think that the "production" version is working ok for all API's?
Re:MongoDB 1.4 Production Release by rit on Thursday March 25, 2010 @03:36PM (#1219290)
Sluggy.com has been using MongoDB in production (with Python as it's main API interface) since ~July '09.

We haven't had a single problem with Mongo or API interfaces. This replaced MySQL + Memcache and was a MASSIVE difference in system load and performance.

Your mileage may vary, but it's very, very rare that I can say I haven't had a single real problem with a third party package (especially one as complicated as a database-type system), more so with early adoption.

(I'm still using Memcache for a few legacy pieces, but in general things I was having Beaker stuff in Memcache such as sessions and Pylons template caches are going into the Mongo Beaker plugin I wrote - http://bitbucket.org/bwmcadams/mongodb_beaker/ )

Re:MongoDB 1.4 Production Release by ccarpenterg on Thursday March 25, 2010 @03:56PM (#1219326)
Yeah, It works for me too with the Python API. But I have to develop some backend app with C++.

Anyway I think I'll try again in the future.

Re:MongoDB 1.4 Production Release by mathias_10gen on Thursday March 25, 2010 @04:10PM (#1219360)
The C++ API should work well as it is what we use in the database. The only issues is that it depends on boost, and any binary copy of the library depends on a specific version of boost. You may want to try compiling libmongoclient for your computer. If you still have issues, please post to our user list or ping us on irc.
Re:MongoDB 1.4 Production Release by ccarpenterg on Thursday March 25, 2010 @04:28PM (#1219403)
I wanted to contact you guys but I'm running out of time this week.

I'll build the production version when I have some free time and then I could tell you. (I was working with v1.3.4)

Re:MongoDB 1.4 Production Release by pibefision on Thursday March 25, 2010 @03:22PM (#1219247)
What problems?
Re:MongoDB 1.4 Production Release by dmerr on Thursday March 25, 2010 @11:40PM (#1220203)
please post details on mongodb-user forums generally, it works
Re:MongoDB 1.4 Production Release by mark_l_watson on Thursday March 25, 2010 @03:40PM (#1219299)
Sweet, I am installing it right now on my MacBook (I always have it running) and if everything looks good I'll also install it on my 2 MongoDB servers. I really like MongoDB for its ease of use with Ruby and its rich query support. I am unlikely to ever need the scalability of Cassandra, and MongoDB's features fit my needs. The new geo location support looks good.
Re:MongoDB 1.4 Production Release by barmstrong on Thursday March 25, 2010 @07:27PM (#1219833)
Anyone found some simple steps to upgrade?

Surprised they didn't include it in the post.

I installed the previous version using these instructions: http://shiftcommathree.com/articles/how-to-install-mongodb-o...

EDIT: Figured it out.

The release notes provide a few more details. http://www.mongodb.org/display/DOCS/1.4+Release+Notes

I pasted the steps I used here: http://www.pastie.org/887556

Re:MongoDB 1.4 Production Release by MartinMond on Friday March 26, 2010 @06:53AM (#1220702)
Where would one use MongoDB? Without durability I'm not really sure I see much applications using it.
Re:MongoDB 1.4 Production Release by MartinMond on Friday March 26, 2010 @07:36AM (#1220756)
Replying to myself (since I found out about this just now): Once MongoDB solves http://jira.mongodb.org/browse/SERVER-467 durability won't be an issue any more
Re:MongoDB 1.4 Production Release by pointernil on Friday March 26, 2010 @06:33AM (#1220687)
Am I the only one a little disturbed by the "name" of this product?

At least in german speaking countries "mongo" is usually only used as insulting calling for people with Down-Syndrom...

Re:MongoDB 1.4 Production Release by nex3 on Friday March 26, 2010 @06:53AM (#1220703)
According to http://en.wikipedia.org/wiki/Mongo, there are a wide variety of uses of the word "Mongo".
Re:MongoDB 1.4 Production Release by pointernil on Friday March 26, 2010 @10:35AM (#1221098)
Yes, I completly understand that (which is as well true for many other words like "ass" and "behind" f.e.)...

Just wanted to point out this little maybe unknown "fact".

cheers