I have noticed that as the day goes on, the Constituent Service appears to lags more and more. There are times a simple constituent search by last name will hang the client for 20-30 seconds. Converting to Household can take up to a minute. The service application pool is only set to recycle once a day. Via SQL Profiler, the procedure doesn't appear to be running that long. I don't see any errors in the Request Response log in the Constituent Service.
What other places can I look for this delay? Should the application pool be set to recycle more? Typically there are only about 3-4 users logged in. When 1 machine hangs, they all hang at the same time.
Has anyone else experienced this? Where else can I look?
Thanks
One thing you may want to check is if the constituent has a lot of associations/affiliations. We found this to be true for college students affiliations with colleges. The fix for us was to uncheck the Show With Group option in the TX_Cust_Type_Affiliate system table.
Show With Group – When this box is checked, individual constituents affiliated with this affiliation type are listed in the Constituent Navigator for the group and are listed on the General tab of affiliated households or organizations.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Joel Freiberg Sent: Monday, October 26, 2015 10:25 PM To: Gloria Ormsby Subject: [Tessitura Technical Forum] Slow constituent response
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!