Strange, I just did a cpu profiling test and I didn't even see or reflect on SLL in that. But I run with a pruned db though.
WoW 2.1, a few months ago, used FuBar_Usage to test. No mod that shows you the results of CPU profiling will do so unless you turn it on and then relog/reload the UI.
The item databases were approximately 40000 items each (no more than 2-3K difference between the two).
Well don't know exactly what happened but I'll post my observation here. Using the latest download 50712 from AceUpdater though in game the title number says 50364. This has happened a few weeks ago (About first week of October) I have now 80K items in the database having built up from Derkyle's ItemDB's 59K. I had successfully and uneventfully whittled down the invalids to 158. But now whenever I try to validate those last few I now DC whenever the count reaches 51. This is the first time I DC'd since the new feature of not DCing went into effect and this only since the beginning of October. I did what I could to eliminate possible causes. I deleted the ItemSync folder from the Add On files and reinstalled using AceUpdater. I disabled all other add ons and nothing changes, I still DC on those last few invalids. I now don't really know what to do and cringe what will happen when another reset or patch comes in.
I have noticed disconnects too recently - not using ItemSync but in an addon I am working on currently. I am still not sure what triggers the disconnects exactly. It does not seem to be a revert to the old behavior. But it is more likely to disconnect you now than a few weeks ago. So I do believe Blizzard changed something. Since it happens on the server, they don't need a patch to change this behavior.
Btw, did Blizzard actually ever confirm anything about the missing disconnects? I am not sure we should consider it an official feature at all sadly. Would be bloody nice though. It is crap annoying having to guard your code against such disconnects. :(
Edit: One theory I have is that they changed the limits on the "flooding" protection for messages sent to the server. Maybe they experienced too many item requests after the change. Who knows?
The theory about flootprotection seems to fit well. If i get back to check validity of items again manual i dont get disconnected, even for items that are known to not exist or dropped on my server yet . I think we just slow down automatic validation .
And it would be great to check for all ids that aren't in your database yet . Every minute or something like that itemsync yould query for such an id, and if the item exists , add it.
And finally is there an option to only show "not-valid" aka red items in the searchresults?
as author of ItemDB and LibInventoryI ran into the same problems.
I had added such a scan for new items in LibInventory and it worked fine until short after Halloween patch. Them the disconnects started. Itweaked its settings a bit and even at only 1 query every 5 seconds I was disconnected after reaching an id around 100. But with that I'd be at 12 items/min, 720/h. The valid ids go up to 35000 currently so it would take over 1 day to scan the whole id spectrum at this speed. But as I said it still results in disconnects. We don't know how exactly Blizzard decides wether to disconnect or not and even if we find a way to not make the disconnects happen they can change it almost anytime which would result in some pissed addon users, again :/
Just to eliminate any confusion I meant Derkyle's ItemSyncDB (57,135 items)which is still extant at http://wowui.incgamers.com/?p=mod&m=4194. Next, thanks for those who posted after me as I had a mini-revelation (no not really but a light blub did come on) about the Brewfest and Halloween patch. There could be something lurking within Blizzard genius coding that MIGHT clear up once this holiday stuff is over. This remains to be seen and I will run the invalid check afterwords and see if the problems persists.
Just like to keep ItemSync users informed that I just attempted to validate the remaining invalid items. I first manually validated the 147 invalid items and winnowed it down to 119 out of 81,387 items. After logging out to save that effort I logged back in and used the auto validate process and was then disconnnected. So there is something in this process that the server doesn't like. The holiday stuff is over but patch 2.3 is going live this Tuesday (11/13/07) Perhaps the patch will stop these DC's but who knows.
As a ongoing update on what is happening with ItemSync. I been using the latest update through WoWAceUpdater and the mod still works except for the Auto Validating feature. The manual validating of invalid items works perfectly. Wish it was the same for the auto validation. I tried this several times what I have seen is the count would typically reach 1600 to 2000 items validated before a disconnect. Perhaps there is something on the server side that limits the number of polls that can be done before the server disconnects the player. Anyone else verify this observation?
I'm giving a try to ItemDB instead of ItemSync right now but i'm curious about this, do i still need ItemPrice-1.1 and ItemPriceTooltip or does ItemDB does the job, and also, how does ItemDB gets populated, cuz ItemSync had a mouseover inspect option for example but i don't see anything in ItemDB ?
I'm giving a try to ItemDB instead of ItemSync right now but i'm curious about this, do i still need ItemPrice-1.1 and ItemPriceTooltip or does ItemDB does the job, and also, how does ItemDB gets populated, cuz ItemSync had a mouseover inspect option for example but i don't see anything in ItemDB ?
If you want vendor-price support, you will need a price-addon that ItemDB supports. Since it uses the GetSellValue function, any addon that supports this should work. ItemPriceTooltip is one option. Check out the link for others.
ItemDB used to have such population code but I moved it into LibInventory-2.1. Also it doesn't really populate on its own but use the WoW clients internal cache that gets populated automaticaly by the game as you see new items.
WoW 2.1, a few months ago, used FuBar_Usage to test. No mod that shows you the results of CPU profiling will do so unless you turn it on and then relog/reload the UI.
The item databases were approximately 40000 items each (no more than 2-3K difference between the two).
Btw, did Blizzard actually ever confirm anything about the missing disconnects? I am not sure we should consider it an official feature at all sadly. Would be bloody nice though. It is crap annoying having to guard your code against such disconnects. :(
Edit: One theory I have is that they changed the limits on the "flooding" protection for messages sent to the server. Maybe they experienced too many item requests after the change. Who knows?
And it would be great to check for all ids that aren't in your database yet . Every minute or something like that itemsync yould query for such an id, and if the item exists , add it.
And finally is there an option to only show "not-valid" aka red items in the searchresults?
I had added such a scan for new items in LibInventory and it worked fine until short after Halloween patch. Them the disconnects started. Itweaked its settings a bit and even at only 1 query every 5 seconds I was disconnected after reaching an id around 100. But with that I'd be at 12 items/min, 720/h. The valid ids go up to 35000 currently so it would take over 1 day to scan the whole id spectrum at this speed. But as I said it still results in disconnects. We don't know how exactly Blizzard decides wether to disconnect or not and even if we find a way to not make the disconnects happen they can change it almost anytime which would result in some pissed addon users, again :/
If you want vendor-price support, you will need a price-addon that ItemDB supports. Since it uses the GetSellValue function, any addon that supports this should work. ItemPriceTooltip is one option. Check out the link for others.