LL Blog: Changes to group announcements

The reduction in database load derived from a *once each day* pruning of a mere 135 groups with more than 200 postings must be absolutely minuscule in the context of growing concurrency from 60k to 70k to ...

I sense desperation here

The reduction in database load gained from this will scale up as the population scales up. Double the number of active groups, and the affect of this change doubles. Cutting away half the old stored notices is really going to impact a very small number of people, and could give a little bit of a performance improvement to get us through the next round of server upgrades.

That's "somewhat" better than a dynamic scrolling, yea. (the once per day part)

However, it effectively means that Fashcon and some other large announcement groups effectively only have a few days of archive, less than a weeks worth. Not only are we at risk of scrollers, we're at risk of catfights amongst people as many newb designers routinely abuse the rules out the gate and send multiple notices. They get dealt with after the fact, but the problem is that its after the fact and the damage is done - people's notices have scrolled off faster and LL's database suffers more load, and well... you can imagine the future dramahz

It would be best for LL and best for our groups if we had a way to throttle the numbers of notices sent via a group role description, such as a one notice allowed per day per week cap, configurable by the group owner.

Vote for the Jira

http://jira.secondlife.com/browse/VWR-7083

Well thats because they are getting ready for the next big influx of users coing soon. LLABs has something up their sleeve and if they need to do this sticker fix to a massive load problem them we in for some heavey flow of out of school kids coming inthe game.........and yes most of them are under 18..........

If they implement it correctly, it should start happening in the background over a few weeks.
SL needs some spring cleaning I suspect, we have crap stored here from people who haven't been inworld for years.

It's the "little bit of a performance improvement" concept that gets me. It might be the difference between the grid beginning to go borky at 61,234 rather than at 62,345. If that were so then it wouldn't really be worth the collateral damage on the non-peak grid.

Even if the global 14-day time-to-live would have some effect, would the separate 200-notice limit applicable to 135 groups really be worth the hassle?

We don't know the numbers.
The only number we do know from LL is that only a minuscule 135 groups post more than 200 notices in 14 days.
Most of the groups that I'm in never send notices or messages, etc. They exist only for land ownership and build permissions. I suspect that the majority of groups are like that.
I'd be interested to see a bar chart of group numbers v. notices.


I get the feeling that LL employees have been urgently tasked to come up with ideas that do anything short of restricting logins (or Inventory) to alleviate grid load.
This measure on group notice count makes me suspect that nobody could come up with any easy answers.

Things like Map, Friends, IMs and email failing at peak load are temporary effects and will recover when LL beef up the power of the database clusters and grid.
This measure on group notices will be a permanent thing. How much help is it really I wonder? Is is simply a bit of imaginary clothing for a naked king.

Not much its only a sticker on a 3 meter whole to plug the leak. Overall the overall usefulness to this only slight.

Evidence? Or are you just pulling this from thin air?

Many of the big high-notice posting groups were created because of the cap on the amount of groups one can join.

People are itching to get info in SL, the systems just aren't there to handle it.

Arrrgh

A search option for past notices would be good - no need to scroll through and load each one to see if it's the info you needed.
If we could actually switch off group notices it'd be nice...I know the tickbox is there but it doesn't work very often!
Abilities to ban members, delete notices, remove objects from past notices would also be nice functions to see...Rather than a cap on what will be stored