Originally posted by DeusEx
Would saving that much off a post truly be beneficial?
Actually, "chain-posting" is much better for the server than one large post.
Here's the issue that maybe didn't get explained enough...
All of ATS is heavily reliant on a large database that is growing even larger at an increasing rate. When a user clicks to view a thread, each post is
sequentially pulled from the database, processed for display, then formatted for view. The
biggest potential performance bottleneck throughout
all our site's codebase is the process of formatting individual posts for display in a thread.
I ran some tests and right between 6,000 and 8,000 characters is where potential problems can crop up. The more "additive" stuff such as BBcode, the
more the server needs to do before your post is ready for display. And the more the server needs to do to larger posts, the
entire board can
slow down if one thread with a big post becomes popular.
For example, the original "Rebel Ridge" posts slowed down the entire board because the initial posts were over 15,000 characters. And not long ago,
another thread with several posts over 20,000 characters caused the entire board to crash... making it difficult to discover why it kept crashing!
Normally, on lesser-trafficed boards, this isn't a problem. But some of our popular threads can experience more than 500 simultaneous viewers at any
given time. Even modestly popular new threads often see around 60 simultaneous people viewing the thread. That's a lot of database work.