Large Threads & Sythe Speed

1kb is about 1000 characters, but the problem is that when you add the time of the post, the user posting, and all the stuff thats part of a query then it does add up. For example the quote BB code is 44 characters for this specific instance, which is about 4.4% of a kilobyte.

Anyways the process of mass querying is what slows the server down, realistically eventually (if he hasn't already) sythe is going to need to get a server that only runs mysql (or whatever sql server). Its not difficult to implement but it costs a lot of money to do so.

 

Quite right, a lot of other larger sites have a server for images, a sql server and a file server. This means that the strain is split across 3 different servers.

 

Sorry if this is a stupid question can somebody explain what 'IO'

 

Input output, basically think of it as a rush hour LA trying to cram into a 4 lane highway. Same thing applies here, too many requests not enough bandwidth to support them all instantly. Unfortunately its not a fiber issue, but more of a SQL issue.

 

I'm not quite sure, but couldn't some things be virtualized to 'overclock' the capabilities of the server?
I know big companys virtualize their system and thus can handle more data / capacity with the same hardware setup.

 

WE all suffered from the deletion/closure, but we suffered more when we couldnt open sythe cause of the load on the servers.

 

You can only transfer stuff so fast. Nothing you can really do except split stuff up... Aka. Make more highways (that's a coding thing like Richard's saying).

 

Well I wasn't aware that the issue was not so much space as it was with just big threads. This suggestion can be closed/denied then, I understand more now.

 

Archiving and permanently deleting threads is really at the discretion of Richard. I'd like to believe he acts with the best intentions and an idea of efficiency when it concerns the health of the forum.

Denied