203 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Traveler 9.0.1.20 Released
Sat, Nov 18th 2017 224
VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild
Tue, Nov 14th 2017 23
Erster DNUG "Domino2025 Jam" Event 23.11.2017
Thu, Nov 9th 2017 5
Domino on Linux Start Script 3.1.3 with changed way to request it
Mon, Oct 30th 2017 4
Great news Notes Domino 10 and beyond
Wed, Oct 25th 2017 4
Correctly Stopping a Traveler Server
Tue, Oct 24th 2017 3
Notes Client 9.0.1 FP9 F1 released
Sat, Oct 14th 2017 4
Top 10
Traveler 9.0.1.20 Released
Sat, Nov 18th 2017 224
VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild
Tue, Nov 14th 2017 23
IBM Notes V9.0.1 Mac 64 Bit English (CN6VDEN )
Tue, Sep 29th 2015 21
Domino 9.0.1 FP9 SMTP Issue
Wed, Aug 30th 2017 15
TLS 1.2 Connection Issues with mail.protection.outlook.COM
Thu, Jan 7th 2016 14
Known issues with Domino 9.0.1 FP9
Wed, Sep 27th 2017 13
Symantec Backup Exec End of Life
Sat, Dec 5th 2015 12
Passing a document to an agent without saving it first
Sun, Apr 6th 2014 11
Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8
Sun, Feb 5th 2017 11
Solution for Notes/Domino related process is still running when applying a Fixpack or Hotfix
Wed, Mar 25th 2015 10


Current Information about NIFNSF
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
Daniel Nashed    

Domino 9.0.1 Feature Pack 8 introduced "NIFNSF" which allows to separate the view/folder index into a separate file.

Let me try to summarized my current experience from my tests and from the field.


There are multiple benefits moving the index to a separate file.

1. Backup Storage Reduction

First of all having the index in a separate file reduces the amount of data that you need to backup.
For mail databases the index is around 10%. If you have DAOS enabled from the remaining data it's about 30%.
So the backup time and backup storage in total is reduced.

2. Size Limit of the data above 64 GB

The total size of a NSF is 64 GB. With DAOS enabled you can increase the logical size of a server based database by moving attachments to the DAOS store.
For DAOS you can have external attachments up to 1 TB. Beyond that size the internal counters might overflow.

But in some cases you still need more that 64 GB for NSF data and the view/folder indexes. With NIFNSF the limit is the 64 GB data in the NSF without the view/folder index.

3. Performance

NIFNSF is intended to deliver better performance than having all data in a single NSF file.

There is a current performance issue. For mail databases there should not be big difference.
But for more complex views in applications the performance with NIFNSF might be not as good as without it.
Tests have shown that it can take double the time.

There is a pending fix that might be delivered with an IF for FP8 which should bring back the performance to almost the same as without NIFNSF.

And for FP9 there is optimization planned to have better performance for concurrent operations. Those changes did not make it into FP8.


So for now you might want to wait at least for an IF before enabling NIFNSF for complex applications.



-- Storage Location for NIFNSF --


There are multiple options to configure where to store the .NDX files which store the NIF data.
What you choose depends on your environment,platform and your requirements.

a.) Have NDX files stored next to your NSF files

b.) Have NDX files stored in a separate folder in the data directory

c.) Have NDX outside the data directory on the same disk

d.) Have NDX stored on a separate disk

There are no one size fits all recommendations. It really depends what storage situation and platform you are running on.

If you can for example on Windows I would store NDX files at least outside the data directory.
On Linux often without a new mount point you might not be able to move the NDX files outside the data directory, because often the data directory is a mount.

If you need to increase your storage anyway because the NSF disk is full, having a separate disk (most of the times virtual disk) makes sense.,
This is a good way for a clean new allocation and it will separate the I/O operations.



-- Enabling NIFSNSF on your Server --


Translog

First requirement is that you are using transactions logging. Circular translog is perfectly OK for that.
And translog is general recommendation for Domino anyway! For stability, fault recovery and also for performance!

ODS 51 or higher

You will need at least ODS 51 for NIFSNSF. But I would recommend using ODS 52 for all databases on your server.

notes.ini Create_R9_Databases=1 will ensure the ODS is updated the next time you run a copy-style compact.

Notes.ini Settings

There are a couple notes.ini settings. The most important setting  NIFNSFEnable=1 enables NIFNSF on your server.

To store the NDX files in different locations (see options above) you can leverage NIFBasePath=path depending on your preferences.

In addition if you want all new databases to be NIFNSF enabled there is another notes.ini setting CREATE_NIFNSF_DATABASES=1 which will ensure that all new databases are automatically NIFNSF enabled.



-- Enabling NIFSNSF on a Database --


Once your server is NIFNSF enabled you can start enabling NIFNSF on your databases via compact.

Please take care not to run the compact operation on all databases. We have seen customers who enabled NIFSNSF also on the DAOS catalog -- even the special database has no views.

I would currently start with mail databases only! And you just specify the right mail directory.

The normal recommendation is to use

compact -c -NIFNSF ON mail/

This will enable the feature and also move existing indexes out of the NSF.
But if the database is in use, the copy-style compact will not be possible.

Instead you could enable NIFNSF on databases without copy-style compact and have a copy-style compact later on with either compact -c or leveraging the DBMT tool which you might have configured anyway.

Once the database is on ODS 51 or higher and NIFNSF is enabled new indexes are created in the NDX file.
But only the copy-style compact will move the views to the NDX file.



-- Checking NIFNSF --


You can check which databases are already NIFNSF enabled and there is also a way to see the size of the NDX. But this command shows all databases.

The most useful commands shows all NIFNSF enabled databases.

show dir -nifnsfonly

show only NIFNSF enabled databases

show dir -nifnsf

show all databases with NDX files also



-- Maintaining Databases with NIFNSF enabled --


I have done some tests. Only with copy style compact the NDX will be compacted.
Many customers are still using compact -B for an inplace, space reduction compact.

There are also other reasons to leverage DBMT which is using copy style compacts and does use space pre-allocation to ensure the NSF is not allocated fragmented.

The copy style compact will also shrink the NDX if needed. A compact -B did not free any space from the NDX file in my tests.

However the free space in a NDX file should be still be reused if released from a purged view/folder index during normal runtime.



-- Tuning for NIFNSF --

A NDX file is a NSF file. The index data needs a container. Therefore if you are running a large server you have to make sure you have sufficient dbcache entries, because the NDX file will also need a cache entry.

By default the dbcache handles depend on the size of the NSF Buffer Pool (which is 1024 MB for 64bit). The number of cache entries is around 3 times the buffer pool size in MB.

3000 DbCache entries should be OK for most servers. But if your server is already on the limit you have to increase the limit.

Here are the relevant server statistics from a current customer example:

        Database.DbCache.CurrentEntries = 4498
        Database.DbCache.HighWaterMark = 4500
        Database.DbCache.MaxEntries = 3000
        Database.DbCache.OvercrowdingRejections = 15220

Your CurrentEntries and HighWaterMark should be alwass below the MaxEntries.
And the OvercrowdingRejections should be always zero!

So in this case it would make sense to increase the number of cache entries to 6000 via:

notes.ini NSF_DbCache_Maxentries=6000

 

---------------------
http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm
Mar 31, 2017
5 hits



Recent Blog Posts
224
Traveler 9.0.1.20 Released
Sat, Nov 18th 2017 3:44p   Daniel Nashed
Traveler 9.0.1.20 has been released and I installed it already. As usual, if you are not waiting for an urgent open issue that is listed in the fix list, it might make sense to wait before installing a new version in production asap. I have installed it already befor the weekend and it looks good for my small environment. Beside the fixes listed below there is a new feature: Support for invitee availability search from Calendar on Exchange ActiveSync clients. Still trying to test it. N
23
VIEW_REBUILD_DIR changed to /dev/shm/view_rebuild
Tue, Nov 14th 2017 2:35p   Daniel Nashed
We just discovered an interesting configuration issue, which generates quite some logging and is a bit annoying. When you specify the view_rebuild_dir without the trailing slash / back-slash, the server will internally append the slash. But if you configured the view_rebuild_dir in the config document without the (back) slash the server will tell you every couple of minutes that the server changed the setting. This happens why the internal path is always stored with the trailing (back) sl
5
Erster DNUG "Domino2025 Jam" Event 23.11.2017
Thu, Nov 9th 2017 1:44p   Daniel Nashed
Nach den Ankündigungen zu Domino 10, der IBM & HCL Kooperation und Domino 2025 haben wir die Agenda für den DNUG Domino Day am 23.11.2017 in Düsseldorf umgestellt. Teil des Domino Days wird der erste deutsche "Domino 2025 Jam" Event sein. Neben dem Uffe Sorensen wir auch ein Kollege von HCL mit dabei sein. Es wird im Vortrag von Uffe u.A. um die aktuellen Informationen zur Kooperation gehen. Ihr könnt alle eure Fragen mitbringen und im "Jam" Teil geht es dann um Feedback fü
4
Domino on Linux Start Script 3.1.3 with changed way to request it
Mon, Oct 30th 2017 5:43a   Daniel Nashed
Just updated the start script to a new version with some minor changes. There was one issue with systemd on shutdown and I made a change in the way config files are used. Most of the new features are coming in either thru projects or when I want something for my own environment. I don't get much feedback or feature requests beside that. One change triggered by a project was how config files apply. We wanted to use the same configuration for all servers. But we wanted special settings f
4
Great news Notes Domino 10 and beyond
Wed, Oct 25th 2017 9:03p   Daniel Nashed
We got great news today. There will be a Notes & Domino 10 in 2018. And IBM also announced that with joined efforts with HCL Technologies they are working on a strategy for #Domino2025. This isn't a new partnership. IBM and HCL are already working together for Tivoli and Rational software. But is was still a big surprise today. Notes and Domino 9.0.1 FP10 is committed for 2017 and I am looking forward to hear more about the Notes & Domino Strategy planned for 2018 with Notes and D
3
Correctly Stopping a Traveler Server
Tue, Oct 24th 2017 2:02p   Daniel Nashed
This is not new but I ran into this a couple of times on customer site. Specially on a Traveler HA server this becomes important. Shutting down the Traveler servertask when the Domino server/service is stopped might lead to hang situations of the HTTP task. The better way would be to shutdown the Traveler servertask first. But even that might lead to undesired results. There is a special Traveler shutdown command "tell traveler shutdown" that can be used to let Traveler finish it's wor
4
Notes Client 9.0.1 FP9 F1 released
Sat, Oct 14th 2017 5:31p   Daniel Nashed
There is also a client IF1 for 9.0.1 FP9 which fixes one part of the issue that I reported. Depending on your configuration MIME messages sent did show up with different fonts on Notes clients. It happened in edit mode or when the embedded MIME browser was disabled. What has been fixed is that the IF1 client shows correct fronts. But earlier clients still shows different fonts (for example if you send a mail with sans serif it will show up in serif). I don't know if that can be fixed at
2
Domino 9.0.1 FP 9 IF2 available with important fixes
Fri, Oct 13th 2017 9:09a   Daniel Nashed
Two of the issues fixed in IF2 have been discussed before in my blog. But there are also two other critical issues fixed. Some of my customers reported DBMT and updall hangs which have been fixed with TDOOAREP8W. And the Private on first use folder issue also has been reported before. If you have installed 9.0.1 FP 9 you should update to IF2! -- Daniel JPAIAQ5SKW PANIC: DbMarkCorrupt! (d:notefileadmin4.nsf Dbiid: 0x3D91E116 0x3C07FE17) JVEKAQSGCC S
6
IBM Champion Program Nominations are open
Tue, Oct 10th 2017 6:05p   Daniel Nashed
The IBM champion nominations have just started today. You can nominate your favorite persons in the community to appreciate what they are doing for the community (--> https://developer.ibm.com/dwblog/2017/ibm-champion-program-nominations/) Libby just expressed it in short words what a champion makes stand out. Let me quote instead of just passing a link! -- Daniel "You may know an IBM Champion if… The best way to understand the IBM Champions program is to know an IBM Champion. D
2
Installing C-API Applications on Linux
Wed, Oct 4th 2017 11:51a   Daniel Nashed
When installing binaries on Linux you have to be aware of the directory structure for the files installed in the opt directory. For installing a servertask the recommended way is to copy it to the Domino binary directory and create a start link. For myself I created a script that handles installation of servertasks and extension managers because I don't want to do those steps manually and my script comes with a wrapper script that benefits of sudo when installing binaries on my developmen




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition