Musicbanter Improvement Thread

Freebase Dali · 01-09-2014, 07:55 PM

It's not an overloading issue. There's no considerable difference between regular members searching for new posts and regular members refreshing or navigating to different threads. It's all queries to a database via web request. If you have too many requests to the web server's connection pool or too many requests from the web application to its database, that will become apparent regardless of whether people are searching new posts or just navigating to new threads.

That wait stipulation is probably more in line with bot prevention. My guess anyway.
I don't know matter-of-factly, but it seems logical due to the fact that people searching for new posts would be not much worse than people simply browsing the website, in terms of web resource demand. Especially considering multitudes of people do just that as guests. Constantly.
As a user, it might be more demanding since the database has to be queried for multiple records, but it's not a logical preventative measure for a single wait when you are allowing a lot of people to execute that query or stored procedure simultaneously, irrelevant of whether they're doing it over and over again, which is less likely than a basic load of people just doing it once or twice every 30 seconds or so.

RoxyRollah · 03-01-2015, 07:14 AM

Its a bulit in defense against spammers boo. Its actually a good thing.Especially if you decide Mb isnt yer thing. Fine whatever,nobody wants yer spam.You have 21 posts whats the issue bro?Link away.

Key · 03-01-2015, 06:17 PM

Quote:

Originally Posted by RoxyRollah

Its a bulit in defense against spammers boo. Its actually a good thing.Especially if you decide Mb isnt yer thing. Fine whatever,nobody wants yer spam.You have 21 posts whats the issue bro?Link away.

Rule #1 of MusicBanter: Do not respond to spam.

YorkeDaddy · 03-01-2015, 06:55 PM

Here's a way to improve MusicBanter:

Ki changing his avatar back to what it was because this new one is givin me the heebie jeebies

:P

The Batlord · 03-01-2015, 07:27 PM

Quote:

Originally Posted by yorkedaddy

here's a way to improve musicbanter:

Ki changing his avatar back to what it was because this new one is givin me the heebie jeebies

:p

+1

Key · 03-01-2015, 07:29 PM

Y'all love it.

**Janszoon** · 03-01-2015, 07:44 PM

Quote:

Originally Posted by Ki

Y'all love it.

I do love it. What is it?

Key · 03-01-2015, 07:46 PM

Quote:

Originally Posted by Janszoon

I do love it. What is it?

They made a teaser trailer for the binding of isaac rebirth and yeah...

RoxyRollah · 03-01-2015, 08:10 PM

Quote:

Originally Posted by Ki

Rule #1 of MusicBanter: Do not respond to spam.

1.(A) Decern if questioner is spammer or acctually posting.He/she is actually a poster.Or a really educated,articulate spammer.

Key · 03-01-2015, 08:12 PM

Quote:

Originally Posted by RoxyRollah

1.(A) Decern if questioner is spammer or acctually posting.He/she is actually a poster.Or a really educated,articulate spammer.

Touché

01-09-2014, 07:55 PM	#1241 (permalink)
Freebase Dali Partying on the inside Join Date: Mar 2009 Posts: 5,584	It's not an overloading issue. There's no considerable difference between regular members searching for new posts and regular members refreshing or navigating to different threads. It's all queries to a database via web request. If you have too many requests to the web server's connection pool or too many requests from the web application to its database, that will become apparent regardless of whether people are searching new posts or just navigating to new threads. That wait stipulation is probably more in line with bot prevention. My guess anyway. I don't know matter-of-factly, but it seems logical due to the fact that people searching for new posts would be not much worse than people simply browsing the website, in terms of web resource demand. Especially considering multitudes of people do just that as guests. Constantly. As a user, it might be more demanding since the database has to be queried for multiple records, but it's not a logical preventative measure for a single wait when you are allowing a lot of people to execute that query or stored procedure simultaneously, irrelevant of whether they're doing it over and over again, which is less likely than a basic load of people just doing it once or twice every 30 seconds or so. __________________

03-01-2015, 07:29 PM	#1246 (permalink)
Key . Join Date: Dec 2010 Posts: 13,153	Y'all love it.