My customer move from on-premise v9 Domino server, to private cloud, v14 Domino server.
As usual, we see that search from view is slower. Very slow. Too slow.
DB is big, very big.
This is not the first time users / customers complain about this.
Ping is correct, connection is good.
This pattern is visible across more customers. Is it due to the new feature to index last 200 documents before launching search ?
Any ideas or recommendations ?
Try with FT_SUPPRESS_AUTO_UPDATING=1 (server's notes.ini), if it makes any difference then the FT auto update prior searching is the cause of slow searches.
I will try this one, it make sense.
Thanks
If db is indexed hourly with frequent modifications makes sense to suppress auto updating or switch to immediate ft update. First one will always be faster from a user perspective.
Hi.
Well, a few factors are involved here, more than only a version change.
Are the database indeed indexed? Are the indexes being maintained?
Do you actually have access to managed the backend Domino infrastructure?
Are indexes on the same disks / partitions? Operating system? Are they in SSD / All flash disks?
In the subject, you mentioned V12, but in the description, you mentioned V14. Are system resources properly allocated in the new infrastructure?
Please don't get me wrong; I'm just listing several items to consider other than the Domino version itself. Search can be noticed slow, depending on several factors.
V14 has enhanced a lot since V9, and it is faster. What are your users using to accessing their mailboxes? Notes Client? If so, are you using local Replica or directly accessing the server in the cloud? ping can be good, but latency is always there when accessing cloud resources and it will always be noticed by end users when switched from an on-premise / LAN scenario.
Regards,
Elvis
I have to a brand new v14 Domino server on SSD disks + rocky linux from an old v9 domino server on Win 2008R2.
Same disk / partition.
I do have access to the backend.
DB is indexed. Hourly maintenance (change from "imediate" to "hourly").
Usage: Search is made by the Notes client.
The search is on one BIG application (we are not dealing with mail files).
Hi.
Understood. And is this big application nsf file locally replicated in the Notes client?
Regards,
Elvis
No Local Replica of this database locally.
Way too big.
Not sure every user would by happy to lose so much space.
And not allow per company policy as some users as temporary
Totally understood.
Well, please let us know the results of changing FT_SUPPRESS_AUTO_UPDATING=1, but please be advised that if such database / app is so big, accessing it via Notes client, would have a slow behavior.
As you have confirmed it is not mailboxes but apps, you may wish to enable and use Nomad client and accessing your app via Web; this way you will eliminate the latency issue of the notes client going back and forth in accessing the app.
You would eventually even get rid of the need of using Notes client.
Regards,
Elvis
Not sure about NOMAD, as the Notes client v9 access was super quick.
I will let you know.
Sure thing it was; but it was accessing the Domino server on local network, not through WAN / Internet.
Mhhh, If one doesn't need a WAN/Internet connection for Notes , is it possible to install Domino/Notes so that it uses the old super-fast LAN communication? INI - entries or ... ?
I even think its more secure, isn't it ?
Joe
Hi Joe.
If you do not support/require to have a public connection, that's ok.
There's no special consideration for that.
You may simply stay behind a firewall and no NAT need to be created, nor any special Domino is required for this scenario.
Your Notes clients could access your Domino server via IP or hostname, as long as your local DNS can resolve that hostname to the IP your Domino install has.
Regards,
Elvis.
Hi Dominique,
While unfortunately not a direct answer, if the behavior is structural and/or coupled to the v12 <--> v14 upgrade, along with switching to cloud, please consider raising a case with Support on this. @Massimo Nadalin suggestion makes sense, however to fully further profile the behavior, raising a case with Support is the best thing to do here imho. When doing so my direct peers or myself will further try to assist to get a more conclusive answer/solution to this.