I only play on a single server, and was collecting data for both Alliance & Neutral, which had my "saved variables %" hovering at around 70%. I recently started a Horde character, and (you guessed it) my percentage is now bouncing around 93%-97%. I have already been periodically cleaning out the TransactionDB, so that isn't a solution. I started removing a few sections from the scan, but since I buy and / or sell items from most categories, and those categories tend to be the big ones, it hasn't helped much. (As an aside, I never really "noticed" the little checkmarks on the categories before, & didn't know that I could skip scanning categories until I started fiddling.)

I went looking in the SV file, along with what limited documentation I could find on the variables, to see if I could (easily) trim anything else.

I infer that "AuctioneerHistoryDB" contains the, well, history information like times seen and other statistics, and "AuctioneerSnapshotDB" contains the raw data from the last scan (both per server/faction, of course).

Is it safe to assume that by the time the Auctioneer scan is complete, that all of the snapshot data has been integrated into the history database? If not, then the rest of this is probably moot.

Because of the way I use Auctioneer, I want accurate statistics, but I generally always hit <Rescan> when posting the few items I am putting up for auction at a time. Given this, it wouldn't be a big deal to me if the "current" results were null before a refresh.

So, would Auctioneer gracefully handle it if I cleared out AuctioneerSnapshotDB (not during a scan, of course!)? I.e., would it just rebuild that structure the next time it tried to access it & found it null?

If that wouldn't be gracefully dealt with, how about something like
AuctioneerSnapshotDB["whisperwind-neutral"]["auctions"] = {}
(etc.)

I am tempted to just try this, but even if it seems to work, it could do something more subtle like throwing the stats off. I would rather hear from people much more familiar with the code than try to walk though it myself "cold".

Thanks for reading. :)

Ah, that makes some sense; you try to match the new scan to the old. Was Auctioneer designed for people who scan the AH multiple times a day, then?

When I started using Auctioneer, I scanned often (to me), to get the stats set up, but "often" to me was generally every day or two. After the stats seemed to settle down, I was only scanning every week or two. Since the auction page speed-up (2.3?), I've been scanning more often, since it doesn't take nearly as long, but still generally daily or less.

Oddly enough, I have noticed in the past that the number of "updated" auctions after a scan wouldn't always be zero, even if I last scanned several days ago. Similarly, the "new" total wasn't always the same as the total scanned in similar circumstances. I suppose it was matching similar (reposted?) auctions, without considering the timestamp. Of course, that could very well have been fixed somewhere along the way, and it's not relevant to this thread.

Back on-topic, I infer that for every "deleted" auction from the scan, it considers it "bought out" or "expired" (if there weren't any (known) bids), based on elapsed time since the last scan. Does anyone happen to know if there are any differences stats-wise between "new" and deleted/sepired auctions?

It makes sense that if everything is "new", that seeing auctions multiple times would start to skew the results, and given my current scanning habits, I can certainly live with not scanning more often than every other day.

Unless there are other issues that haven't been raised yet, I would just need to know if the current version of "classic" Auctioneer will gracefully rebuild a null AuctioneerSnapshotDB as it needs each realm/faction, or if I should just kill the "auctions", "auctionIdsByItemKey", and possibly "updates" for each realm-faction entry? Presumably, there's code to build it, since it would be needed for when the add-on is first run (when there isn't a prior state to load), but that might only get triggered at load time.

Posted By: RockSliceI'd recommend switching to AucAdvanced, which doesn't have this problem, due to a different file structure.

Yea, I know. AucAdvanced is the future. From what I can determine, though, it does not yet do everything I want, as easily as can be done with "classic" Auctioneer using (or importing) it's stats.

Posted By: RockSliceAs for your questions, Auctioneer was made both for people who scan several times daily, and for those that scan once or twice a week.
Remember when looking at the different counts that auctions can last for up to 48h (slightly longer if they're bid on), so scanning within 50h should show "updated" auctions.

I was mainly expressing surprise that people would be willing to sit through multiple 30-45 minute scans in a day (before the speed-up). I only really noticed the odd showing of "updated" auctions back when the max duration was 24 hours, and I was scanning only every week or two.

Posted By: RockSliceAs for rebuilding the AuctioneerSnapshotDB, Auctioneer should gracefully rebuild it, meaning it will do nothing to help with your SV size problems.

But it will help. since I now know that I can just blow away the whole structure after a scan, or (relatively) easily edit the SV file, if I don't, and hit the parser's token limit. In fact, I think I'll just plan on doing the latter, unless I start getting stung multiple times.

Last question in that case: Is an obvious error thrown when the token limit is reached, or do I need to make sure to look for the "x% full" message?

Some of us are crazy and scan many times a day...
I have far too much "stuff" in circulation and it may take me hours to empty my mail box.
I go and fill up my inventory from the mailbox, then head to the AH and post it all, this frequently takes over ten minutes itself, so I scan and run btm while I am waiting.
Because of this I scan many times a day just from my normal process of emptying my mailbox because it takes too long...

It's excessive though and wastes far too much time. I am currently slowly changing my settings to buy less stuff just because of the time involved!