Why is LS1Tech so SLOW???
Is there any kind of upgrade being planned that will improve the speed of LS1tech???
Sorry about the bitching... it just drives me bonkers!
Thanks guys! Other than the speed, I LOVE the site!
Yes, its the board software that is limiting the speed. No, we won't lose everything if we were to switch software. However, there is no plan to switch software. There is nothing better to change to AFAIK. The problem lies in the database support that is currently found in the board software, or lack thereof.

Trending Topics
The Best V8 Stories One Small Block at Time
cyphur_traq,
Sorry, maybe I should've done a seach for "slow" before I posted... I didn't mean to waste server space with something as silly as asking why the board is moving a warp turtle speed.
Would you like some help? Free of charge of course....
Not all databases are written in SQL. You also have to be skilled in other languages to rewrite that code such as PHP. Not sure on the exact size of the database but I will tell you its HUGE.
vBulliten currently only supports MySQL AFAIK, which is why Brains started to code backend support for other database applications - which would allow a performance leap and would largely eliminate our bottleneck.
Now, if my understanding of this is flawed, please correct me. But this is how I've come to understand the situation.
For eg. (from the bottom of the home page) ...
Currently Active Users: 1025 (453 members and 572 guests)
That means only 453 users actually have write privileges. Then at most 453 could be trying to update the DB at once (unlikely). You could do analysis of the transactions to understand the number of DB writes per minute and then optimize accordingly. My guess is ~50 of those 453 are trying to update the DB at any given 10 second interval. The rest are just browsing.
antagonist - you're an idiot
VB does a *LOT* of database writes; updating status on the user table every page click, updating thread views, etc. As you're aware, the MyISAM storage engine doesn't support anything but a table level lock -- which means every one of those writes are blocking. Most complete quickly and don't cause a problem at all. The problem is when you have a costly query that blocks, and then you stack 500 requests right behind it in a matter of a second or two. Then the performance goes right in the can, and everyone waits. There's the option of switching to the InnoDB storage engine, but then we lose fulltext search, get slower overall performance, and a LOT more overhead. That didn't work either, performance was actually worse than MyISAM believe it or not.
PostgreSQL doesn't offer FULLTEXT indexing "in the box", but there's an add-on module that does. The biggest benefit is multi level concurrency control, which MySQL doesn't offer at all. Simply put, that means a client can read any record, even if its being updated, without blocking everyone else from doing their business. It means you can make multiple updates on the same table without issues -- ie. two or 100 people posting at once, no difference. If two people post at the same time under MySQL, everyone waits.
Last edited by Brains; Nov 15, 2005 at 12:46 PM.
MySQL is a GREAT database, for really fast application that rely on heavy amounts of selects. For applications with a mixed load, or many complex inserts/updates/deletes, you run into problems. vBulletin falls into the latter, especially when you start putting a few million posts into the database. We're being forced to temporarily archive off old posts to get the database size managable, so performance doesn't go completely in the drink.
. SQL = structured query language. Queries, get it? It doesnt matter what language is used to create the program using the database
. You can execute SQL from WITHIN almost any language.
If you know what you are doing.


