Quizzes & Puzzles3 mins ago
Why so slow?
7 Answers
Why does it take ages to call up a topic on Answerbank and what needs to be done to improve the situation?
Answers
Best Answer
No best answer has yet been selected by rov1200. Once a best answer has been selected, it will be shown here.
For more on marking an answer as the "Best Answer", please visit our FAQ.I dont work for answerbank, and have no idea of the actual problem, but here is my comment on it.
Like many web sites that store lots of data (Amazon, BBC etc) there are two main parts of it.
There is the "front end" which is the bit we see - the web page, the topics, the adverts, all the text on the screen etc.
Then there is the "back end". This is normally a relational database.
When you select a topic the "front end" has to go to the "back end" and say "give me all the entries for topic xzy"
This ovbiously takes some time. On a powerful system it could take less than a second.
But suppose 100 people are all asking the "back end" to do something at the same time.
This will obvously slow down the system and instead of taking a second it can take 5 seconds, or 10 seconds or whatever.
The more users you have the slower the system gets.
There are ways round this.
Get a faster server, get a better database, redesign the web site, spread the database over more than one server and so on.
None of these are quick, easy or cheap and all cost money.
I have no idea if that is why there are problems, but it may help you understand why there is no "quick fix".
Like many web sites that store lots of data (Amazon, BBC etc) there are two main parts of it.
There is the "front end" which is the bit we see - the web page, the topics, the adverts, all the text on the screen etc.
Then there is the "back end". This is normally a relational database.
When you select a topic the "front end" has to go to the "back end" and say "give me all the entries for topic xzy"
This ovbiously takes some time. On a powerful system it could take less than a second.
But suppose 100 people are all asking the "back end" to do something at the same time.
This will obvously slow down the system and instead of taking a second it can take 5 seconds, or 10 seconds or whatever.
The more users you have the slower the system gets.
There are ways round this.
Get a faster server, get a better database, redesign the web site, spread the database over more than one server and so on.
None of these are quick, easy or cheap and all cost money.
I have no idea if that is why there are problems, but it may help you understand why there is no "quick fix".
To give you an idea how expensive providing a fast system is think about Google.
MILLIONS of people do Google searches every day (maybe every second) but the response is very quick.
How do they do that?
Well they have THOUSANDS of severs (individual computers) all over the world.
Nobody knows how many, and Google wont say (for security reasons) but it is estimated they have between 200,000 and 500,000 servers world wide.
Can you imagine the cost of all that technology.
Not sure how many servers answerbank has, but for each server they buy that is more money.
MILLIONS of people do Google searches every day (maybe every second) but the response is very quick.
How do they do that?
Well they have THOUSANDS of severs (individual computers) all over the world.
Nobody knows how many, and Google wont say (for security reasons) but it is estimated they have between 200,000 and 500,000 servers world wide.
Can you imagine the cost of all that technology.
Not sure how many servers answerbank has, but for each server they buy that is more money.
It boils down to the site being poorly designed.
I have no idea what system it's running (ASP on IIS I think), but whatever, it's slow because it's been poorly designed.
There's nothing you can do about it, it's up to the guys that maintain the site. It's nothing more than a load of forums, so should be simple to run.
You don't need tons of hardware like load-balancers and all kinds of servers to run a forum.
I have no idea what system it's running (ASP on IIS I think), but whatever, it's slow because it's been poorly designed.
There's nothing you can do about it, it's up to the guys that maintain the site. It's nothing more than a load of forums, so should be simple to run.
You don't need tons of hardware like load-balancers and all kinds of servers to run a forum.