Despite the recent optimization, the Deep Connections gramplet should be used sparingly… due to its heavy burden.
Perhaps a Deep Connections Quickview Report would be a more resource-friendly alternative?
In a thread discussion today about sharing an Event for a Witness, it became apparent that users will often want to know the connections the person (or family) has with those holding the Primary (or Family) role(s).
So a Quickview context menu option for the Event tab would be useful.
Why can’t we let the developers do some tuning of the db-api and moving frontend logic to the back end before we go totally bananas with everything that takes more than 25 sec. to do?
All of these performance stuff that everyone complain about are things that can be fixed one step at a time now that Gramps use JSON instead of BLOBS, because they can start move time consuming frontend logic to the backend, regardless if it is postgresql or sqlite…
My tips for everyone is to have a little patient for now…
