Trifork Blog

Putting the pedal to the Mongo metal

March 1st, 2013 by
|

At Trifork we’re always looking to get the best performance out of our systems. As a 10gen partner that means that we also try to squeeze the most out of our MongoDB deployments in terms of read and write throughput. Experience has shown that it matters greatly whether those deployments are performed on dedicated hardware or on virtual machines: especially having enough and fast RAM and disk IO can make all the difference.

If you’re interested in reading up on this topic, make sure to check out this article on SoftLayer’s blog. It shows how hosted MongoDB deployments can perform when given the appropriate hardware, and how having a hosting provider that understands the technology running on their infrastructure can help you to achieve the performance that your applications require.

If you’re in The Netherlands and want to learn more about MongoDB, whether you’re a newbee or an experienced user already, you should sign up for  the upcoming Mongo User Group meetup that’s taking place coming Tuesday as well: SoftLayer will be there to tell more about their hosted MongoDB offering, 10gen’s Alvin Richards will talk about what’s planned for the upcoming releases of MongoDB (spoiler: it includes search!) and we’ll have Open Space sessions where you can decide for yourself what topics you’d like to see covered. Hope to see you there!

2 Responses

  1. March 3, 2013 at 10:51 by Olivier Gacho

    That’s a great post on SoftLayer blog Joris. What has been the largest mongodb configuration that Trifork amsterdam has architected and implemented ?

  2. March 7, 2013 at 14:35 by Joris Kuipers

    Hi Olivier,

    sorry for the late reply, this blog apparently doesn’t notify me when there’s a comment.
    Most of our applications are using MongoDB for the features and ease-of-use that a document-based DB provides. One customer is currently storing ca. 11TB in a Mongo cluster with two shards (at least, last time I checked it was two). Each of the shards is a 3-node replica set.

    Note though that throughput/volume matters as least as much as the actual amount of data stored: you don’t need to have TBs of data in order to benefit from MongoDB and its sharding functionality.