Welcome to the #dominoforever Product Ideas Lab! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated jointly by the IBM & HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino page.

NSF/NIF and DGQF: Internal $Readers/Authors index

One of Domino's main appdev scalability barriers with medium/large NSFs occurs when a user has access to a very small subset of documents. For example, consider the scenario:


1. A view or folder has tens of thousands of docs in it

2. A user only has access to a small (e.g. 1-10) docs within that


Any lookups, searches, GetDocumentByKey, etc. against that view or folder will result in major page-scanning operations as Domino tries to find docs. This can cause painfully long delays in code execution as Domino searches the entire view (maxing out CPU) to end up with the small set of docs that the user can actually see. This cost is incurred each time the code is run.


It would be awesome if NSF/NIF stored a "Readers/Authors" index that Domino would automatically use first to assist in the subsequent NIF scan operations.


DGQF seems to already have some capability near this area in that it seems "smart" in searches involving AND conditions. So there might not be a lot of extra work needed here. Such an index could probably be leveraged in many areas of the product for a significant performance/scalability boost.


If there are admin concerns (e.g. disk space, etc.) then this could perhaps be an NSF toggle.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 31 2018