|
The performance problem is ongoing. Note that the logs are mysql query logs, not tomcat logs. What further info would be helpful to troubleshoot this?
Stephen,
I have turned on the log level to be "debug", with the following setting in sakai.properties. log.config.count=1 log.config.1 = DEBUG.org.sakaiproject The I will see all sql queries in my tomcat log, since the SqlService is logging at the debug level. However, I am dealing with the most current 2.2 code now, and you reported based on 2.1.x. - Zhen As our term is almost finished and we're upgrading to Sakai 2.2 when released, we will test this on 2.2 (when there's a migration script available).
If anyone else has this problem on 2.1.x, it might be worth pursuing, but we're more interested in whether the problem persists in 2.2 or not. We'll add more info when available. Repeated this on a trunk build (r10586) and am seeing identical symptoms - extremely large numbers of queries to the alias and preferences tables, leading to performance issues.
mysql log from assignments list view run against 2.2 (our 2.1.x production db upgraded to 2.2 with the upgrade scripts). Sequence of events:
- Login as 'marquard' - Search for POL3032F site in Worksite setup and navigate to the site - Go to assignments tool to list the assignments (12 visible for this site) The major problem (queries to SAKAI_ALIAS) has been resolved. However, I'm still seeing lots of queries to SAKAI_PREFERENCES like this:
select XML from SAKAI_PREFERENCES where ( PREFERENCES_ID = 'marquard' ) In the example I tested (logging just the queries generated after clicking on the tool reset icon), there were 127 of these - a large number of identical queries sequentially upfront, and then about 4 to 5 following each assignment query. Reopening this for the SAKAI_PREFERENCES issue (and downgrading priority, as the performance impact of this is lower). However, if you'd like to resolve this issue and open another one for the SAKAI_PREFERENCES behaviour, please go ahead.
Performance is now acceptable on our staging 2.2 server with our migrated 2.1.x production db.
To QA this on a QA server would require a realistic data set of a reasonable size (several hundred students in a course site with > 10 assignments listed, and existing assignment submissions). |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
I couldn't find anyting in Assignment module which invokes SAKAI_ALIAS table. The table is consulted by several other implementations, like site email notification, Worksite Setup tool, etc.
Could you reproduce the problem and get the "select SAKAI_ALIAS.ALIAS_ID ..." in the tomcat now? My think is it was an accident...
Thanks,
- Zhen