Answers.Body: <p>It sounds like you might be running the dedupe on a large database with slow MySQL performance; I've certainly seen this before.  The database doesn't even have to be that big; I've seen this on databases with as few as 20,000 contacts.</p>
  
  <p>The pre-set dedupes that can't be edited use a fundamentally different approach to deduping that runs MUCH faster, but it must be hard-coded.</p>
  
  <p>There's an unpublished extension from Veda (see item 1 <a href="http://www.vedaconsulting.co.uk/civicrm-dedupe-workflow-ui" rel="nofollow">here</a>; most subsequent items are part of Civi 4.7) that adds a framework for more hard-coded dedupes, along with a large number of extra pre-built dedupes.  That may be better for your situation.  I'm not sure it's tested on Civi 4.7 though, so try it on a copy of your database first!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-03T16:12:11.233Z
Answers.Text: Thanks, Jon. Guess I'll have to a little more than the basic optimization. Btw, this is on MariaDB.
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-04T20:06:02.783Z
Answers.Text: @BruceW It looks like Eileen may have introduced a new feature to make life easier in your situation: https://issues.civicrm.org/jira/browse/CRM-18958.  It's not clear to me whether this is going into Civi 4.7.9 or 4.7.10 though.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-05T21:17:06.950Z
Answers.Text: Thanks @Jon-G That would be helpful as a workaround but for the most part expanding education about database server optimization would be more preferable for plenty of other reasons. I can see building off of this wikipage:  https://wiki.civicrm.org/confluence/display/CRMDOC/Speeding+up+Mysql
Answers.UserDisplayName: BruceW
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-02T15:20:31.010Z
Answers.LastActivityDate: 2016-07-02T15:20:31.010Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>On CiviCRM 4.7.8/Joomla 3.5.1, I've experimented with variety and can't seem to get this to work. The preset reserved rules, import, inclusive in contact record and main dedupe rules are all working. If I create a new General Rule with just Email set for 10 characters with a weight of 10 and a Threshold of 10 on a group of 10, 50 and 100 contacts in a group with both known and no dupes. Running this rule just runs and runs without any results whether or not the frontend times out to 500 error.</p>
  
  <p>The default Reserved Rules run lickety-split.
  Please advise.</p>
  
Tags: <database><duplicate-contacts><rules>
Title: Are custom Dedupe General rules working for anyone?
ThreadText: # Are custom Dedupe General rules working for anyone?
  
  (Asked by: username_0 on 2016-07-02)
  
  On CiviCRM 4.7.8/Joomla 3.5.1, I've experimented with variety and can't seem to get this to work. The preset reserved rules, import, inclusive in contact record and main dedupe rules are all working. If I create a new General Rule with just Email set for 10 characters with a weight of 10 and a Threshold of 10 on a group of 10, 50 and 100 contacts in a group with both known and no dupes. Running this rule just runs and runs without any results whether or not the frontend times out to 500 error.
  
  The default Reserved Rules run lickety-split.
  Please advise.
  
  **Tags:** database, duplicate-contacts, rules
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2016-07-02. Score: 1
  
  It sounds like you might be running the dedupe on a large database with slow MySQL performance; I've certainly seen this before. The database doesn't even have to be that big; I've seen this on databases with as few as 20,000 contacts.
  
  The pre-set dedupes that can't be edited use a fundamentally different approach to deduping that runs MUCH faster, but it must be hard-coded.
  
  There's an unpublished extension from Veda (see item 1 [here](http://www.vedaconsulting.co.uk/civicrm-dedupe-workflow-ui); most subsequent items are part of Civi 4.7) that adds a framework for more hard-coded dedupes, along with a large number of extra pre-built dedupes. That may be better for your situation. I'm not sure it's tested on Civi 4.7 though, so try it on a copy of your database first!
  
  > **Comments:**
  > **username_0**: Thanks, Jon. Guess I'll have to a little more than the basic optimization. Btw, this is on MariaDB.  
  > **username_1**: @username_0 It looks like Eileen may have introduced a new feature to make life easier in your situation: https://issues.civicrm.org/jira/browse/CRM-18958.  It's not clear to me whether this is going into Civi 4.7.9 or 4.7.10 though.  
  > **username_0**: Thanks @Jon-G That would be helpful as a workaround but for the most part expanding education about database server optimization would be more preferable for plenty of other reasons. I can see building off of this wikipage:  https://wiki.civicrm.org/confluence/display/CRMDOC/Speeding+up+Mysql  
  
  ---
  
  