I admit that I had to stop running WoWCensus because it seemed to slow things down on my connection. (Better than dsl, not as good as cable, but subject to clogs)
Can you put an option in there which disables data collection when in an instance? That would be a major benefit. Last thing I want is WoWCensus hogging bandwidth/processor time when I'm trying to fire off a heal.
Another fun thing I used to do was make a /2 Trade announcement of the current survey.
[2. Trade][Faline] Current on-line realm population 12,349 Alliance
People always seemed to be interested in that. Though I can't see this being a good idea to add as an option to WoWCensus. Might end up as spam if too many people are doing it.
Lastly, I did have a question:
Why does it take so long to interrupt WoWCensus when you want to do a /who on a toon? That was always one of my pet peeves about WoWCensus.
Faline
Bandwidth load and census announcement
Are you sure it is not another Addon slowing things down... like ANY member of your group using Gearscore, which is said to take a lot of bandwith?
Also, if you want to, just press the "Pause" option of Censusplus when you want to take a break from censusing.
As for the interruption length, I let Rollie give you a better answer, but I suspect the reason is simply that the programmed interval between /whos is that high.
Also, if you want to, just press the "Pause" option of Censusplus when you want to take a break from censusing.
As for the interruption length, I let Rollie give you a better answer, but I suspect the reason is simply that the programmed interval between /whos is that high.
-
BambisFaline
It seems to be doing better this time around.1974ER wrote:Are you sure it is not another Addon slowing things down... like ANY member of your group using Gearscore, which is said to take a lot of bandwith?
But to address the GS question, the slowdown is definitely WoWCensus. Slowdown didn't occur when WoWCensus was disabled.
It's quick enough to acknowledge the user request, so I can't imaging that is the problem. But we can wait for the Source to let us know.As for the interruption length, I let Rollie give you a better answer, but I suspect the reason is simply that the programmed interval between /whos is that high.
Yeah, Census really doesn't use up that much. It's one request and response every couple of seconds. Census CAN use a lot of memory depending on how big your local database is.
Some of the more problematic mods that take up processor/bandwidth are things like MapQuest, DBM, Recount, etc.
Some of the more problematic mods that take up processor/bandwidth are things like MapQuest, DBM, Recount, etc.
phpbb:phpinfo()