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
I failed to mention that we are currently on version 11.0.4.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris JensenSent: Tuesday, October 27, 2015 9:43 AMTo: Joel FreibergSubject: Re: [Tessitura Technical Forum] Slow constituent response
Joel Freiberg:I have noticed that as the day goes on, the Constituent Service appears to lags more and more. [...]Has anyone else experienced this?
Joel Freiberg:
I have noticed that as the day goes on, the Constituent Service appears to lags more and more. [...]
Has anyone else experienced this?
Yes, we've noticed this, too, since v12, and more so with v12.5. Slower as the day progresses, meanwhile there are no obvious performance issues with either the database, its server, nor client machines.
Joel Freiberg:Where else can I look?
Where else can I look?
I, too, suspect the issue is with the REST application pool somehow. I'm not an expert on IIS performance troubleshooting, but have a sneaking suspicion I may become one in the months to come...
Unknown said: I failed to mention that we are currently on version 11.0.4.
Ah. I notice mysterious, non-SQL-server related, slowness more often on v12+, progressively, as (perhaps not coincidentally) more and more communication with the db has migrated to REST.