CiviCRM Community Forums (archive)

Hey all,

I have a site with a large number of contacts (~200,000) currently undergoing heavy load.  I've been eying mytop, and along with normal-looking (if complex) queries pulling user info from the civicrm db, certain useless queries have been popping up, locking up mysql until I kill them.  I've seen two forms of these queries:

SELECT * FROM civicrm_address

and

SELECT * FROM civicrm_location

No WHERE clause, and no ORDER BY clause.  I have no idea where these queries are coming from, but they are slow with such a large db, and killing them clears things up temporarily.  Does anyone have an idea 1) where these might be coming from? or 2) a good way to trace their origin?  The query builder makes grep'ing for this kind of thing impossible.

FYI, this is running the latest stable release of 1.7 (PHP4) and Drupal 5.2.

Thanks!
-marco

Issue filed: http://issues.civicrm.org/jira/browse/CRM-2137

Summary: Lobo and I talked about this on IRC, which led me to adding some code to the _query function that looked for one of the bad queries, and sent a backtrace email to me when it happened (by calling the main function in dalin's very useful civicrm_error module for Drupal). 

After some problems with matching the query string (watching out for extra spaces and doing a substring match), I finally got a backtrace of the bad queries: they are being called via the isLocationEmpty function when a new contact is created.  See the issue for more details.