OmnomIRC temporarily disabled

[Netham45]

OmnomIRC is temporarily disabled until we can track down the source of the site slowness.

iOmnom and iOmnom_Mini are unaffected.

[DJ Omnimaga]

Netham, I am afraid that OmnomIRC is effectively the source of the slowness. When the entire site domain runs slow like this, but script execution time is not very high and 51.aspirationhosting is up, then it's because our account is throttled for too many resources usage.

One concern I have is that this month we had 6.5 million of hits. Before we had about 3.5 and the highest we had was 5 millions I think. I can only think of the two following scenarios:

-Either the recent OmnomIRC updates introduced bugs causing an overload of resources or the new OmnomIRC is simply too demanding on the server.
-Either we get too much traffic to sustain OmnomIRC anymore on a shared hosting.

In the latter case, this would either mean that you have to host the entire OmnomIRC elsewhere or we say farewell to it.

That said, something needs to be done, because this is starting to affect our activity a whole lot.

[Netham45]

I think I just came up with a way where I can take almost all of OmnomIRC off of the server.

Do we have unlimited subdomains?

[Eeems]

JSONP would probably help with this probably

[DJ Omnimaga]

I think so, although the domain is hosted on 1and1 and managed on Aspiration, so it could be 100.

But keep this in mind: OmnomIRC alone was 12 millions of hits last month.

By the way how much bandwidth did we use last month?

EDIT: Eeems what is JSONP?

[Netham45]

JSONP wouldn't be any good, it's incompatible with AJAX.

Yup, I got everything I need.

I'm going to make a subdomain on Omnimaga.org, omnom.omnimaga.org. I can then set the document.domain to omnimaga.org for OmnomIRC stuffs, then I can get around the same-origin policy and remove the bounces(logbounce.php, userbounce.php, messagebounce.php), which are the main 3 that are generating traffic.


Edit: JSONP is just a way of moving data.

[Eeems]

JSONP wouldn't be any good, it's incompatible with AJAX.

Yup, I got everything I need.

I'm going to make a subdomain on Omnimaga.org, omnom.omnimaga.org. I can then set the document.domain to omnimaga.org for OmnomIRC stuffs, then I can get around the same-origin policy and remove the bounces(logbounce.php, userbounce.php, messagebounce.php), which are the main 3 that are generating traffic.


Edit: JSONP is just a way of moving data.

it would require a little changing to your end and it would work fine for me. iOmnom can handle JSONP fine with a tiny bit of modification. JSONP also allows you to not have to follow the same-origin policy and it would work pretty great.

[Netham45]

it's also incompatible with AJAX, has a considerably higher client-side load requirement, and constantly refreshes the pages.

[Eeems]

it's also incompatible with AJAX, has a considerably higher client-side load requirement, and constantly refreshes the pages.

I was pretty sure they were pretty close to the same thing. I also haven't noticed the higher client load requirement with json/jsonp when I used it.

[DJ Omnimaga]

So all the files would be hosted on your IP, but the domain name would be used?

[Netham45]

Almost all of them. I still need the two files to get the userlist.

[DJ Omnimaga]

Ah ok

I definitively think the php files in question received too many requests and it caused overload on the server. I hope it doesn't cause problems on yours, though.

[Netham45]

It won't be putting much, if any, extra strain on my server.

[Eeems]

It won't be putting much, if any, extra strain on my server.

are iOmnom/iOmnom_mini getting moved over as well?

[Netham45]

For now, no, though you may need to update it to use view_omnom. I'm removing logbounce.

Omnom is re-enabled now too.

OmnomIRC's presence on Omnimaga.org has been reduced to two userlist files. Shouldn't put any load on Omnimaga anymore.