Hi everybody,
For anyone who has upgraded to v15- have you noticed Tessitura running more slowly post-upgrade? We've seen a small hit in performance when searching for constituents. Not enough to hamper operations, but enough to be noticed. We are self-hosted and have more than minimum specs on all of our servers.
Thanks, all!
Cheers,Kathleen
Hey Kathleen,
Are you RAMP or self-hosted. I know RAMP clients have been experiencing latency with Tessitura for a couple weeks now. I don't know if that was all versions or just V15. If self-hosted, I'm not certain if this is happening there as well.
- Chris
We are self-hosted.
We had similar, but much more severe, symptoms when we upgraded to v14. At the time I think it was the fact that address search had been make much more complicated by contact points. I think I heard something to the effect that GDPR support with contact permissions would also exact a performance hit. In the prior case (v14) they were able to mitigate the major performance issues with a point update in a few months, but some performance loss is, I think, inevitable.
Hi Kathleen,
We've not had any known issues with performance after v15 upgrades. We've gone ahead and opened a ticket on your behalf so that we can investigate if this is something related to an underlying issue, machine requirements etc. Also noting here that the latency issues reported in the Hosting environment has since been resolved earlier this month.
Thank you,
Melissa
Hi Kathleen --
Just in case -- you're likely already doing this -- one thing to check on is regularly reindexing / rebuilding indexes (weekly or monthly). Especially after an upgrade, this is often helpful to performance. See the Tessitura Database Utilities documentation on [UP_REBUILD_ALL_INDEXES]. We've had a couple of moments since v14 where indexes have resulted in slower than expected performance, often following upgrades or major data imports / updates.
DGomez
Echoing Daniel's response...
Our virtual DBA took the Tessitura reindex job and tweaked it to add some additional reindexing and split some of the process so that it's not all being done at once.
Our performance metrics improved significantly after we began doing this on a regular basis.
We're running the standard SQL Server Rebuild Indexes Maint Plan on a weekly basis? I believe this accomplishes the same thing as the UP_REBUILD_ALL_INDEXES Daniel mentions, although they may be slightly different.
Re: indexes, I recommend Ola Hallengren's "SQL Server Index and Statistics Maintenance" for nightly index rebuilds of only the indexes that need it.
https://ola.hallengren.com/sql-server-index-and-statistics-maintenance.html
Much lower overhead than rebuilding *all* indexes.
Ola's backup script is excellent, as well, imho.
I totally agree.