Not signed in (Sign In)
    • CommentAuthorfrozndevl
    • CommentTimeMay 14th 2008
     
    Since 2.4.2 came out, my scans specific categorys are going slow intermittently; I scan armor and weapons as standalone. Has anyone else experienced this?
    • CommentAuthorKinesia
    • CommentTimeMay 14th 2008
     
    The patch changed how Blizzard deals with people's names in the Auction House.
    If there are a lot of different sellers this may make things take slightly longer.
    We're looking into it now.
    • CommentAuthorcryingstar
    • CommentTimeMay 16th 2008
     
    before patch 2.4.2 my scan rate was about 80 to 90 auctions pr sec

    Now it is 15 to 30 pr sec
    •  
      CommentAuthordinesh
    • CommentTimeMay 16th 2008
     
    I am not seeing any significant slowdown. Are you sure your connection speed hasn't been worse than normal?
    • CommentAuthorfrozndevl
    • CommentTimeMay 16th 2008
     
    I could generally get 1 page per second, or 50 auctions, pre 2.4.2. Now it is intermittent... sometimes it hangs on the 2nd page for a while, sometimes it oes through at normal rate. My connection hasn't changed since the patch.
    •  
      CommentAuthordinesh
    • CommentTimeMay 16th 2008
     
    well, blizzard has made some changes on the back end, with respect to auction seller name. I have been running a dev modified version which already "pauses" when it finds auctions with no names, so perhaps I've just always been seeing this behavior, and it is just now new to you now that blizzard is enforcing it as well.

    I'll let the team know, and see if one of the devs wants to look into it.
    •  
      CommentAuthordinesh
    • CommentTimeMay 16th 2008
     
    also, using AA, I'm not sure it was ever possible to get 80-90 auctions per second. We were still limited to one page of 50 items per second, afaik. (unless using getall)
    • CommentAuthorMikk
    • CommentTimeMay 16th 2008 edited
     
    Here's a test: When you've run a full scan, run another one. It should be much faster since all the GUID->names are already resolved and cached. If it's fast, it's indeed the resolver slowing you down.

    Though to be fair, there's no real need to test even. We KNOW that the resolver changes will slow things down. Scanning a full AH with nothing pre-cached will take 5-10 minutes depending on AH size, just because the resolver limits it to 128 names looked up every 30 seconds. We're hoping that blizzard will at the very least back the change out -- it really was better when we had to do throttling manually :S
World of Warcraft™ and Blizzard Entertainment™ are trademarks or registered trademarks of Blizzard Entertainment, Inc. in the U.S. and/or other countries.