Seasons Greetings…

Xmas picture
2011 has been an amazing year for me and ForgeRock. I’m so thankful to ForgeRock for offering me the opportunity build a strong engineering team in Grenoble, and to Matthew, Gary and Mark for taking on brilliantly the lead on so many fronts. OpenDJ is a very strong product, successfully deployed in production at many customers. Matthew is driving excellence in the project development and there’s been more contributions to the project in the last 6 months than in the 4 years of the life of OpenDS. The quality of all ForgeRock products is improving under Gary’s leadership. And the documentation is thickening under Mark’s pen.
I’m looking forward to the new year as we will, with no doubt, continue to thrive and have fun. And we will grow our engineering team worldwide and more specifically in Grenoble.

But now it is time for some vacation and quality time with the family. So I wish you all a Merry Christmas and a Happy New Year 2012. May peace, love and prosperity follow you always.

Benchmark proves OpenDJ fastest directory server !

Isode has just released a benchmark of their M-Vault R15.1 directory server, and has run some comparative tests against OpenLDAP and OpenDJ.

While the benchmark demonstrates that M-Vault is one of the best directory server out there (the new release has some really impressive search performance) , I paid more attention to the write performance, and I really like those results that are showing the OpenDJ is the fastest directory server for write operations, even when modifications are mixed with searches.

Benchmark write performance summary

Captured from Isode benchmark white-paper.

Thanks Isode for running those tests, and making those numbers publicly available.

An important tuning flag for OpenDJ with 64bit JVM…

If you’re running OpenDJ with a 64bit JVM with less than 32GB of heap size, be aware of the need to explicitly set the -XX:+UseCompressedOops option (unless you want to disable it).

Compressed oops is supported and enabled by default in Java SE 6u23 and later, when running a 64bit JBM with a value of -Xmx lower than 32GB. You can find more information about Compressed Oops in Java technical notes here:

However, OpenDJ internal database, in order to estimate properly the occupation of the DB cache and tune the cache eviction threads, needs to take into account the compressed oops option. For this is relies on the JVM option to be set explicitly. If the option is not explicitly set, the database may consider the cache full when it’s not, and run cache eviction too early, resulting in less optimized performances.

So, with 64bit JVM, make sure you add the -XX:+UseCompressedOops option to the start-ds line in the config/ file. Then run bin/dsjavaproperties and restart OpenDJ to benefit from the new settings.

OpenDJ success story : Ziggo

A few months ago, we worked with Ziggo in Netherland, to help them transition their legacy environment to ForgeRock I3 Open Platform. Part of the transition, they’ve replaced Sun Directory Server Enterprise Edition (DSEE) with OpenDJ, running in 3 data-centers (and different sites), and over 2.5 Million entries, in a very smooth and well controlled migration process.

They’ve now been running OpenDJ and OpenAM in production for a few months and we’re really happy to be able to share the details of the story with you. Get the Ziggo Case Study (PDF).

You can find more details about OpenDJ on ForgeRock web site.