It seems like every time the auction is revised, the revision doesn't work and adds bugs... This recent update is no exception (In case you haven't noticed, using the level filter gives unpredictable and incorrect results).
As a SQL programmer, I am guessing that the querying in the auction is not done in SQL... Just because it would be really hard to make mistakes in SQL that would return bad results like the auction does. (And maybe you are not using SQL in misguided hope of reducing server load?)
Anyway, clearly you are trying to refresh the data so we can know when an auction closes or changes. I don't see how this can be done more efficiently than just requerying with a very efficient query as the UI indicates a need. Countless other sites support thousands of users doing far more data intensive work using pure SQL.
And it seems migrating to SQL would bring along all sorts of free benefits... You could automatically fix the annoying thing where "sorting" doesn't sort the whole data set, but just sorts each page individually...
And, it would be easy to add a filter for user chosen key words like "Bane" or "Flaming"
And you could stop requiring users to pick a category... I.e. It would be easy to support the user just searching for "Icy Burst" to get a list of all Icy Burst weapons of any type, instead of having to repeat this search and scoll through pages on each weapon to gather this info.
I don't want to seem ungrateful for having an auction, but it could be sooo much better... I feel like a chef being given a free but under-cooked steak. What is the best way to say "thank you", but also ask for it to be cooked a little more...