I’ve got a problem with slow searches in Domino Designer. When I do a file search in the Domino Designer with a scope set to “Enclosing projects” (i.e. the current database) the search progresses quite nicely until its about 7 files from the end where it pauses for an increasingly long time. The progress dialog claims to be searching the database.properties file. For some of our databases this pause is only a few seconds, for some others databases it can be minuets. This is making an otherwise useful feature really painful to use.
I took a look at the XML for the database.properties for one our applications where the search takes seven minutes on database.properties, I compared this to another application where it takes eight seconds. The slow one has 215 lines of XML, the faster one has 150 lines, this difference in size due to more entries in the ACL for slow one. That is the only real difference I could find and it doesn’t really explain the difference is search times.
Is anyone else experiencing this problem? Better yet, does anyone know how to avoid it?
Is this issue specific to only on DDE or multiple? If you can reproduce on a different machine, you should open a PMR with IBM support and provide a sample database so we can reproduce and investigate. If it’s only happening on a single machine and you want a quick fix, you can perform a clean install and see if it clears up the issue or open up a PMR with support and we can investigate that client/DDE.
It is happening on multiple machines. I have also raised a PMR with IBM who are currently investigating.
Further research and experimentation suggests a correlation between the number of documents and/or attachments in the database and the slowness of the search. The applications that took seven minutes to process database.properties was on our dev/test server and contained over 700,000 documents with 12GB of attachments. The same search on a design elements only copy of this database searched database.properties almost instantly. The search however did still noticeably “pause” for almost a minute when processing a form that had several jar files embedded in it, leading us to think a problem with searching attachments.
IBM support are aware of this. It also potentially provides a work around for anyone experiencing this problem if you can setup your dev/test environment so you only do these kinds of searches on templates or versions of the database with little or no documents in them.