Update - April 17 2017 - IBM has fixed the issue in 9.0.1 FP8 IF1.

In my last post about NIFNSF, Christian Hensler left this comment:

Image:Domino NIFNSF update - you probably don’t want to enable it
I couldn't find anything on the internet, so off I went to the Design Partner forum and sure enough there is a post in there from Michael Bourak. Now this is a NDA'd so I'm maybe skirting the rules here, but there is indeed an IBM reproduced issue with performance with NIFNSF. So this AM I did some testing and I was able to reproduce the issue. Based on my testing, on average, the current NIFNSF implementation is twice as slow as non-NIFNSF databases.

So you many not want to implement it just yet.
Darren Duke   |   March 31 2017 10:33:37 AM   |    domino    |  
  |   Next Document   |   Previous Document

Discussion for this entry is now closed.

Comments (7)

Gravatar Image
1 - Ursus Schneider       03/31/2017 10:54:30 AM

Thank you for sharing - was just about to do it this weekend - guess I'll wait :o)

Gravatar Image
2 - Sean Murphy       03/31/2017 11:45:56 AM

Twice as slow? Thanks for the info.

Gravatar Image
3 - Craig Wiseman       03/31/2017 2:24:02 PM

Thanks for sharing!

I *do* think you meant "half as fast", though.

Gravatar Image
4 - Daniele       03/31/2017 5:09:34 PM

I can confirm that is slow I/O after NIF separate.....

Every view.refresh is slow...

This separation is awaited feature..

Bug the implementation is not so good

Gravatar Image
5 - Lars Berntrop-Bos       04/05/2017 7:42:11 AM

Anybody know how to reverse? I tried setting the associated INI settings to 0, and ran a COMPACT -C -nifnsf off, but the ndx files are stil updated...

Gravatar Image
6 - Fredrik Norling       04/10/2017 3:49:29 AM

Will be interesting to see your findings when doing the same tests now that IF1 with a potential fix is released.

Gravatar Image
7 - Michael Bourak       04/10/2017 4:04:40 AM

FP8 IF1 fixes the problem, now performances are "on par" with classic NSF

Would be interesting to do real benchmarks with ndx files on a separate high speed disk...