Tumbleweeds on NLOC

Brian Baskin

Brian Baskin

Rikutsu-poi
I had just written a post about how dryed up all the forums are getting around here, with sometimes 2-3 hours in between posts, and not many replies at that. Then, I posted this thread and realized probably why. 2 minutes to refreshing to get through Resource conflict errors, and then another 30 seconds of Server too busy, then finally when it loaded up, my page had expired, and my post was never posted....

I'm going to bed

OK, this is the 3rd time I've tried to post this, and it keeps coming back resource conflict :(
 
i probably have the slowest piece of sh!t computer out there and i don't have that many probs. once in a while i'll get a server busy error but other than that it's doing okay for me.

i for one am not going anywhere until they kick me out!:D -chris
 
The way I understood it was that we made the switch to better the web site. I always get the same thing that you guys get (server busy,ect.) and it seems people are having trouble posting pics too. I don't remember any of these problems on the old site.
Maybe, its just taking a while to get things going. I hope they get it fixed though. Oh, one more thing how can we be having problems with not enough space or what ever it is, when the Mustang forums have alot more users with no problems?
 
LOL, I hate to make comparisons, but going around one of my other favorite forums, I just spotted their stats:
Currently Active Users: 764
There are currently 499 members and 265 guests on the boards.
Most users ever online was 950 on 09-11-2001 at 04:28 PM.

Then again, they run their own servers, and they have their own problems (the message database gets frequently corrupted, so posts are made, but don't get updated on the main listing). I guess all forums have their problems in some way or another, here's to hoping they fix it soon.
 
Yep, it's frustrating . . .

There are a zillion hosting companies out there and this site, in the grand scope of things, requires very little bandwidth. It troubles me that they can't find a host to support our needs, as members, at an affordable price.
 
JJ - Having FORUMS isn't the problem. It's not a SPACE problem, it's a bandwidth problem. I had the opposite problem on the old site - Remember the occasional "banlist" error? That's because we'd run out of storage space. But we had plenty of bandwidth.

And they are working on it. Just remember, guys, that the people running the site aren't paid to run the site and they do it in the time they have available (this site doesn't pay anyone's rent). In this case the site is a drain on the coffers and not a banner-besotted revenue generator.

If you want to do something positive to help out, remove the pictures from your signature and reduce the signature lengths. One picture costs more than a page of text. This isn't a fix - it is, however, a stop-gap that can help.
 
Last edited:
I get all those errors as well, a lot at night, especially over the last few days. I've been logging off and giving up. Maybe linking to pics on other sites is using bandwidth?
 
Hmmm... that may be correct since everything has to be img tagged right now, but I'm not certain of it since vBulletin replicates and stores a LOT of stuff in databases. UBB definitely just used links (which is why sometimes people's sig images took forever to load).
 
Brian Baskin said:
But, none of the sig pictures are stored on NLOC, it wouldn't use up their bandwidth ...
Click to expand...

Brian, I thought the same thing at first.

But think about it:

It is not storage space that is the problem, it is bandwidth. The pics (code, references, whatever you want to call them) are still information traveling through the same pipeline that users use to access the board. Sooooo, the less info to go through the "pipeline" the more room there is for users.

Am I right?
 
It's going through the same pipeline, but through different pipelines :) Let's say you have this:

A....B....C
\....|..../
.\...|.../.
..\..|../..
...\.|./...
.....D.....
.....|......
.....|......
.....E.....

A being, let's say, imagestation.com.
B being NLOC.net
C being w3.cablespeed.com (my img host)
D is your internet provider
E is you

When you load a web page, NLOC.net sends you just a text listing of the page. As your browser parses through that text, it comes across an IMG tag for www.imagestation.com/picture.jpg (ex.). At that time, your machine makes a connection to A to download that image. As your machine keeps parsing, it finds an IMG tag for w3.cablespeed.com/picture.com C, so it jumps out to C to grab that file.

The pipeline from B-D is only used to send text, the pipelines from A-D and C-D are used for pictures, and the pipeline from D-E (your ISP to you) is used to send everything. However, the bottleneck is in the pipeline from B-D, as NLOC's provider is limiting their bandwidth amount. The pipeline from D-E (your ISP) should be very large, large enough to handle most users, and should rarely be full.

The only information that is sent from B-D is plain text in these posts, and the occassional < img src = "http://www.somesite.com/picture.jpg" > which is still just plain text.

OK ok, I'm bored at work. So sue me :)
 
Brian,

Can you clarify the difference between A and C?

The way you expalined is the way I originally thought. But, then I started second guessing myself.
 
A and C are just generic places on the web where pictures are stored at. Could be imagestation.com, webphotos.com, members.aol.com, etc. Really, I could have done it with just an A and B, and left out C, but I had to one-up myself :)
 
OK, A and C are the same. That's what I thought.

You say that the text file is parsed and locates the IMG tag. With ya so far. Then, you say my machine jumps out to grab the image. Where is that image displayed? It is displayed on the board in the message which means that image and its contents had to come in through the board's bandwidth. No?

Maybe the difference is in the way the PHP is assembling and parsing the HTML files for display. If nobody sheds any light on this, I'll ask my PHP expert here at the office---I'm, obviously, still learning.
 
Here's a good way to look at it. Right click on this web page, and a menu will pop up. Click on 'View Source' and a notepad window will open up full of HTML code. That text is exactly, and only, what NLOC sends out to you. Internet Explorer receives this big bunch of text, and then it's done talking with NLOC. It then starts parsing through it line by line, and displaying it on the screen, as it comes across an image, it will then make a connection to the server where that image is stored, and download it/display it. It just does all this so fast that it seems like the page instantly pops up. The image was taken from a different site, your browser just sticks it in there in the middle of the NLOC text. Another way to see this is to right click on any picture you see (like the one in my sig) and click Properties. It should show you the URL to where the picture is located.
 
Kev, think of a set of headers - in this case with two primaries, that being two web sites, and one collector, that being your ISP.

The image and the text do eventually come together, but if the image isn't somehow stored on the NLOC site (whether by replication, uploading, embedding, whatever), then it isn't using the site's bandwidth - only the storage site's bandwidth.

Just the code is for the location of the image is sent to your browser, which, when it parses the code, goes to the storage site and looks for the image.
 
You must log in or register to reply here.

Similar threads

J
Pimpxshift issues
Replies
11
Views
1K
Jericho347
J
O
2500 miles daily driving with Holley HP EFI
2
Replies
37
Views
2K
slow94
S
L
The Red/Black Lightning is Back on the Street (But not without issues)
Replies
10
Views
589
lightngsvt
L
core-rider
LMR Cruise-In 2023 and KOTOR TX weekend
Replies
12
Views
2K
Kidsixpack
Kidsixpack
I
Minor but annoying transmission issue
2
Replies
26
Views
3K
Ieharris
I
Back
Top