We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
The Forum now has a brand new text editor, adding a bunch of handy features to use when creating posts. Read more in our how-to guide
The Site's Playing Up Again
Comments
-
Try 10.00 tonight SS

Hopefully the maintenance shut down for 4 hours tonight will help!0 -
Its getting worse- snail pace:A 17/10/07-Started Rosemary Conley :ATotal loss so far= 4 stone 7lbs!In the magazine Sept 08:T0
-
It's not particularly slow for me - but I can't format, which is especially annoying in a long post. Also, when you check to see who's thanked you, it sends you to the top of the page but still no list of who's thanked you.Also, what's happened to the "quick links"?0
-
JonnyThunder wrote: »Because vBulletin is using a mySQL backend it's more likely this is where the bottleneck is. mySQL isn't really designed for that many concurrent connections in the first instance, but when you have 6000 people browsing the site at any one time - you're REALLY putting it under strain. Especially considering vBulletin is making many queries on each page refresh.
MySQL can handle that sort of load, given a suitable software design and hardware. When talking about concurrent connections to the database server, rather than the forum software, 2-3,000 is reasonable as a maximum and if they are connecting on demand and always busy when connected it'll be significantly lower. Really depends on the load properties of the application and whether the connections are in a constantly busy connection pool or sitting there idle most of the time.
Martin got it right: working with the software designers to do what's necessary to support scale-out (I assume) and optimising the database layer of the application. The hardware upgrades are also useful. I've had good experiences on the few times I've dealt with vBulletin people.
One approach that might work for vBulletin, after replication has been exploited as far as practical, is to have the application consolidate queries to multiple database servers, each handling an adjustable subset of the boards. That'll work until a single board section with a database server and database slave or two dedicated to it is too big to respond decently. LiveJournal does something similar to this with Friends lists, building the friends page from queries to the server holding each friend (though if memcached is running properly, that serves the results instead of the database servers).0 -
Its slow for me today on and off0
-
Very very slow for me, is getting silly tbh0
-
is there any point in us even attempting to use the site this evening?know thyselfNid wy'n gofyn bywyd moethus...0
-
Keeps giving me the "Could not display this page" and very very slow
Work like you don't need money,Love like you've never been hurt,And dance like no one's watchingSave the cheerleader, save the world!0
This discussion has been closed.
Confirm your email address to Create Threads and Reply
Categories
- All Categories
- 354K Banking & Borrowing
- 254.3K Reduce Debt & Boost Income
- 455.2K Spending & Discounts
- 247K Work, Benefits & Business
- 603.6K Mortgages, Homes & Bills
- 178.3K Life & Family
- 261.1K Travel & Transport
- 1.5M Hobbies & Leisure
- 16.1K Discuss & Feedback
- 37.7K Read-Only Boards