What's wrong with the servers?

[Silent Fang]

sythes not loading for me at all... ive tried ww2 also and this is the first time its worked in the past few hours

 

[The Black Tux]

Fatal error: Out of memory (allocated 8388608) (tried to allocate 491520 bytes) in /home/sythe/public_html/includes/class_postbit.php(300) : eval()'d code on line 209

I sent to Richard (Via FB) a message about the hosting & servers in June 10, which I'm sure he ignored. But the servers are still crappy.

There are thousands of dedicated servers providers. And as I work with DDoSHostingSolutions (Where mobile.sythe.org is hosted), I can talk to the owner and get a cheaper Staminus Server.

I just don't understand why the FUCK are we still in the crappy hosting.

EDIT: Over 20 reloads were necessary to edit this...

Warning: preg_match() [function.preg-match]: Compilation failed: failed to get memory at offset 19 in /includes/functions.php on line 686

I could even myself provide a free server (dedicated)... but that won't happen (They don't trust me enough, bs right?)

Netfronts is really shitty.

 

[They be trippin]

Fatal error: Out of memory (allocated 8388608) (tried to allocate 491520 bytes) in /home/sythe/public_html/includes/class_postbit.php(300) : eval()'d code on line 209

I sent to Richard (Via FB) a message about the hosting & servers in June 10, which I'm sure he ignored. But the servers are still crappy.

There are thousands of dedicated servers providers. And as I work with DDoSHostingSolutions (Where mobile.sythe.org is hosted), I can talk to the owner and get a cheaper Staminus Server.

I just don't understand why the FUCK are we still in the crappy hosting.

Fatal error: Out of memory (allocated 3670016) (tried to allocate 295088 bytes) in /home/sythe/public_html/includes/class_datastore.php on line 365

Got that while trying to post this. It's time to upgrade.

 

[Alma Mater]

This has been happening on/off for at least 3 months. Getting pretty ridiculous if you ask me.

 

[Nick]

This has been happening on/off for at least 3 months. Getting pretty ridiculous if you ask me.

Errors have been happening for years I'm afraid. We patch up one and another comes up.

 

[Sythe]

Fatal error: Out of memory (allocated 8388608) (tried to allocate 491520 bytes) in /home/sythe/public_html/includes/class_postbit.php(300) : eval()'d code on line 209

I sent to Richard (Via FB) a message about the hosting & servers in June 10, which I'm sure he ignored. But the servers are still crappy.

There are thousands of dedicated servers providers. And as I work with DDoSHostingSolutions (Where mobile.sythe.org is hosted), I can talk to the owner and get a cheaper Staminus Server.

I just don't understand why the FUCK are we still in the crappy hosting.

EDIT: Over 20 reloads were necessary to edit this...

Warning: preg_match() [function.preg-match]: Compilation failed: failed to get memory at offset 19 in /includes/functions.php on line 686

I could even myself provide a free server (dedicated)... but that won't happen (They don't trust me enough, bs right?)

Netfronts is really shitty.

Got that while trying to post this. It's time to upgrade.

Yeah sorry about this. Basically when the IO speed was bad I optimised all the caching and sometimes mysql tops out the server's memory at the moment. I'm still adjusting it back down to an optimum level.

Look, I'm aware the hosting has been suboptimal over the past few months. And I too would like to move to a better set up. The problem is this: Simply moving to another provider is not going to fix anything. It will take a lot of time and energy, and we'll be back where we started with an essentially unmanaged mysql instance running a large unwieldy vb3 database and being minced on the side by php instances which routinely eat 200 mb of ram.

We actually need to move to a mysql (cloud) service, imho. Thus putting the database in the hands of people who will manage it day and night. I've been looking for a good provider but I haven't found one yet.

What I'm saying is that there's no point knee jerk reacting and running to the nearest other hosting company. We'd just be spinning our wheels and getting nowhere.

 

[They be trippin]

Yeah sorry about this. Basically when the IO speed was bad I optimised all the caching and sometimes mysql tops out the server's memory at the moment. I'm still adjusting it back down to an optimum level.

Look, I'm aware the hosting has been suboptimal over the past few months. And I too would like to move to a better set up. The problem is this: Simply moving to another provider is not going to fix anything. It will take a lot of time and energy, and we'll be back where we started with an essentially unmanaged mysql instance running a large unwieldy vb3 database and being minced on the side by php instances which routinely eat 200 mb of ram.

We actually need to move to a mysql (cloud) service, imho. Thus putting the database in the hands of people who will manage it day and night. I've been looking for a good provider but I haven't found one yet.

What I'm saying is that there's no point knee jerk reacting and running to the nearest other hosting company. We'd just be spinning our wheels and getting nowhere.

Have you looked into Cloud Flare? That's what we have used for Zarpor (a RuneScape Private Server that I use to help manage.)

If this is a terrible suggestion however, please disregard it. I am quite disqualified when it comes to these sorts of things.

 

[Sythe]

Have you looked into Cloud Flare? That's what we have used for Zarpor (a RuneScape Private Server that I use to help manage.)

If this is a terrible suggestion however, please disregard it. I am quite disqualified when it comes to these sorts of things.

That's a static CDN company. Also we need a well established company. No start ups.

 

[The Black Tux]

Yeah sorry about this. Basically when the IO speed was bad I optimised all the caching and sometimes mysql tops out the server's memory at the moment. I'm still adjusting it back down to an optimum level.

Look, I'm aware the hosting has been suboptimal over the past few months. And I too would like to move to a better set up. The problem is this: Simply moving to another provider is not going to fix anything. It will take a lot of time and energy, and we'll be back where we started with an essentially unmanaged mysql instance running a large unwieldy vb3 database and being minced on the side by php instances which routinely eat 200 mb of ram.

We actually need to move to a mysql (cloud) service, imho. Thus putting the database in the hands of people who will manage it day and night. I've been looking for a good provider but I haven't found one yet.

What I'm saying is that there's no point knee jerk reacting and running to the nearest other hosting company. We'd just be spinning our wheels and getting nowhere.

Grave and I know a provider... (I showed him)

8 physical cores. Dual CPU.
16GB RAM
10TB on gigE port.
4x1TB Disks with h/w RAID10

Under $300. (I won't give exact price)

I'm pretty sure that could handle Sythe.

 

[The Black Tux]

That's a static CDN company. Also we need a well established company. No start ups.

It is obviously not a CDN. Works like the reverse proxy (that you also happen to have with nginx VPS), but.... BETTER.

Have a look into the PRO version.

 

[Sythe]

Grave and I know a provider... (I showed him)

8 physical cores. Dual CPU.
16GB RAM
10TB on gigE port.
4x1TB Disks with h/w RAID10

Under $300. (I won't give exact price)

I'm pretty sure that could handle Sythe.

Which is basically what we're already on. Doesn't fix the essential problem, as I've already said.

It is obviously not a CDN. Works like the reverse proxy (that you also happen to have with nginx VPS), but.... BETTER.

Have a look into the PRO version.

It is a CDN with a reverse proxy. We already have a reverse proxy and static hosting and neither of these things are the source of the problem. As I've already said, we have a database problem. If anything we need a managed sql service.

 

[The Black Tux]

Which is basically what we're already on. Doesn't fix the essential problem, as I've already said.

It is a CDN with a reverse proxy. We already have a reverse proxy and static hosting and neither of these things are the source of the problem. As I've already said, we have a database problem. If anything we need a managed sql service.

Can't be compared to CloudFlare...

And if that's what we are on, the way things are setup, are really really shit.

A node like that could easily handle at least 2 times Sythe if it was managed well.

But I won't keep discussing this, as we all know... nothing is going to change (Can't fight the fact that humans learn from experience)

So, do whatever you want Richard, but we all hope it's quick.

 

[Sythe]

Can't be compared to CloudFlare...

And if that's what we are on, the way things are setup, are really really shit.

A node like that could easily handle at least 2 times Sythe if it was managed well.

But I won't keep discussing this, as we all know... nothing is going to change (Can't fight the fact that humans learn from experience)

So, do whatever you want Richard, but we all hope it's quick.

That's pretty insulting. The host has had hardware problems with their DASD over the past few months as I've already outlined. This lead to reconfigurations to maximise caching. Some of which still need adjusting. As to it being a 'really really shit setup'. How many forums with 300,000 users do you manage on a day to day basis? All you've suggested so far is that we use a CDN reverse proxy, which does not even address the problem. If anything your suggestion is shit and a waste of my time.

 

[Sordeo123]

That's pretty insulting. The host has had hardware problems with their DASD over the past few months as I've already outlined. This lead to reconfigurations to maximise caching. Some of which still need adjusting. As to it being a 'really really shit setup'. How many forums with 300,000 users do you manage on a day to day basis? All you've suggested so far is that we use a CDN reverse proxy, which does not even address the problem. If anything your suggestion is shit and a waste of my time.

ANY host with such a high traffic volume as this website is going to spike somewhere. You can't help it. Just got to wait it out. I agree with this statement. I don't know many people who try to maintain a website such as this one...

 

[SuF]

*Cough*The random attacks we get don't help*Cough*

 

[The Black Tux]

That's pretty insulting. The host has had hardware problems with their DASD over the past few months as I've already outlined. This lead to reconfigurations to maximise caching. Some of which still need adjusting. As to it being a 'really really shit setup'. How many forums with 300,000 users do you manage on a day to day basis? All you've suggested so far is that we use a CDN reverse proxy, which does not even address the problem. If anything your suggestion is shit and a waste of my time.

In fact, a staff did it. Not myself. Are you sure about your mods then?

Also, I don't manage one site with 300K users. But I sure manage a server with more than 500 users in the last 15 minutes. And, with the information you have given, you have a much better dedicated(At least 2x) than the one I have for shared hosting.

I also happen to work at DDoSHostingSolutions... so yeah I do have experience.

No offense or insult intended.

 

[Sythe]

In fact, a staff did it. Not myself. Are you sure about your mods then?

Also, I don't manage one site with 300K users. But I sure manage a server with more than 500 users in the last 15 minutes. And, with the information you have given, you have a much better dedicated(At least 2x) than the one I have for shared hosting.

I also happen to work at DDoSHostingSolutions... so yeah I do have experience.

No offense or insult intended.

Sythe.org has 500 users in the last five minutes all accessing the same table of the same database, trying to read and write to it.

If you don't understand the difference between database concurrency issues, hardware IO issues and reverse proxy/caching issues then how can you possibly help?

To clarify: We only have the first two problems, one because of the way vbulletin is structured, the other because our host has been rubbish over the past few months. We do not have the third problem -- which is the only problem for which you have proposed a solution.

If you want to do some research into how hard it is to run large sites smoothly on mysql go look at facebook: http://www.facebook.com/MySQLatFacebook
They have a dedicated research staff to keep their mysql instances up.

Anyway long story short, saying our set-up is shit doesn't help fix any of the problems. I've already addressed the memory errors and I'm keeping a closer eye on them, with a script to inform me when the site is giving out 500 errors. The host has fixed its disk and IO problems.

I'm still looking into migrating us to a cloud hosted mysql solution, but that can't be rushed.

 

[Annex]

Sythe.org has 500 users in the last five minutes all accessing the same table of the same database, trying to read and write to it.

If you don't understand the difference between database concurrency issues, hardware IO issues and reverse proxy/caching issues then how can you possibly help?

To clarify: We only have the first two problems, one because of the way vbulletin is structured, the other because our host has been rubbish over the past few months. We do not have the third problem -- which is the only problem for which you have proposed a solution.

If you want to do some research into how hard it is to run large sites smoothly on mysql go look at facebook: http://www.facebook.com/MySQLatFacebook
They have a dedicated research staff to keep their mysql instances up.

Anyway long story short, saying our set-up is shit doesn't help fix any of the problems. I've already addressed the memory errors and I'm keeping a closer eye on them, with a script to inform me when the site is giving out 500 errors. The host has fixed its disk and IO problems.

I'm still looking into migrating us to a cloud hosted mysql solution, but that can't be rushed.

To add to this, you weren't around back in 2005-2007 when the issues where significantly more severe than they are currently. The servers are in much better condition and the turnaround from downtime is alot faster than it has previously been. There used to be whole days where no matter what you couldn't get through to the website.

 

[kill dank]

I have been instructed to post this:

http://en.wikipedia.org/wiki/MongoDB



I am not affiliated with any of these hooligans, though.

 

[Sythe]

I have been instructed to post this:

http://en.wikipedia.org/wiki/MongoDB



I am not affiliated with any of these hooligans, though.

Sounds like you're stooging for them.

Vbulletin is not designed for any database other than MySQL. Honestly it takes about five seconds of research to find this information.

See for yourself:
https://www.vbulletin.com/faq.php#faq-121

And for reference there is no way I am going to run a production server on an unsupported backend.