Issue 24 in power-matchmaker: DQguru should warn the user if the match engine finds an unusually high number of matches
codesite...@google.com
Owner: mo.jeff
Labels: Type-Enhancement Priority-Medium OpSys-All Milestone-Release1.0
Component-UI Performance
New issue 24 by mo.jeff: DQguru should warn the user if the match engine
finds an unusually high number of matches
http://code.google.com/p/power-matchmaker/issues/detail?id=24
In the event that the DQguru finds an unusually high number of matches
(Jonathan said that this would be roughly over half the number of toal
records or higher), performance gets degraded significantly, largely
because waiting to to transfer the result table data over the network. It
also slows down viewing results in the match validation mode, and also
loading the match pool in subsequent match engine runs.
In such situations, it's probable that the user's transformations are
either too loose, resulting in too many matches, or their data has serious
quality issues. In any case, it would be worth notifying the user that
their transformation is finding an unusually high number of matches, and
prompt them to either continue storing these matches into the result
table, or to stop the engine entirely so that the user can tweak their
transformation.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
codesite...@google.com
Summary: DQguru should warn the user if the match engine finds an
unusually high number of matches (Bugzilla #1711)
Comment #1 on issue 24 by mo.jeff: DQguru should warn the user if the match
engine finds an unusually high number of matches (Bugzilla #1711)
http://code.google.com/p/power-matchmaker/issues/detail?id=24
(No comment was entered for this change.)