Issue Details (XML | Word | Printable)

Key: ADV-505
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: yiNXs
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Auctioneer

Option to enable/disable incremental scanning

Created: 24/Nov/09 07:40 AM   Updated: 10/Dec/09 10:04 PM
Component/s: Scan
Affects Version/s: None
Fix Version/s: None

Environment: N/A


 Description  « Hide
Make the incremental scanning functionality of Auctioneer configurable: add an option to enable/disable this functionality.

At this time (version is 5.6.4424, as reference) the incremental scanning functionality is always active and can't be turned off.

This option is meant for users with more then one AH addon and who are very active on the AH.

The incremental search functionality replaces the warcraft-internal QueryAuctionItems() function with a custom version. This is a wrapper function around the internal QueryAuctionItems() that processes each auction search, even done by other addons, with the goal to update the Auctioneer database. Whenever there is heavy AH activity, this extra processing can end up causing problematic machine slows, long freezes and even disconnects.

Because this functionality is not a critical function of Auctioneer (it's has no added value whenever regular full, or category scans are performed), being able to turn it off speeds up performance significantly for heavy users and makes Auctioneer much more compatible with other addons like QuickAuctions.

A discussion about this option, the problems it can solve, and a working hard-coded fix can be found in the following forum post:

http://forums.norganna.org/discussion/11246/a-way-to-deactivate-incremental-scanning



 All   Comments   Change History   Transitions   FishEye   Crucible      Sort Order: Ascending order - Click to sort in descending order
AnrDaemon added a comment - 10/Dec/09 10:00 PM - edited
I'm not really interested in disabling this functionality, but more - in having it configurable.
I.e. I do not want it to react on partial scans (these "... before stopping"), hijacking my data with false absent items.