|
shallowdeep -> RE: TOS (3/28/2010 1:42:45 AM)
|
quote:
ORIGINAL: VaguelyCurious
quote:
ORIGINAL: DarkSteven
/Explains to holly/
If I tell 16 to go into 21 five time, it will, because I'm so Domly. I never let numbers push me around.
Tell me: did you used to work for Enron?
I'm sure DarkSteven just has a decent working knowledge of finite field arithmetic.
21/16 = 5 is perfectly true in GF(59)
No domliness required. Just mathematics… and not the sort practiced at Enron.
Somewhat on topic:
quote:
ORIGINAL: ThatDamnedPanda
Pardon my ignorance, but does it really work this way? Just a general question for the group - I'm not doubting that this is true, but I don't understand how it works. Does it only slow down the users trying to load that particular page, or does it really slow down the entire server? Can someone explain it, because my curiosity is really piqued.
quote:
ORIGINAL: VideoAdminAlpha
It can pull down the speed of anyone doing a search that might involve that particular post, to anywhere that the whole thread or post might be displayed in a list of topics, any thing that might involve anything that requires the server to look search that thread and wind up on that topic, multiplied by the users that might be on that thread, or even looking at that whole category (off topic, general bdsm etc) or doing searches at the same time etc. Then multiply that by the fact another user might be in another area whose functional capability has possibly been slowed in response to the others areas being slowed, and you can see what can happen. It was not to this degree of seriousness at this point, but if continued unchecked it could possibly cause a bigger problem than what was happening.
I don't think this explanation is particularly accurate from a technical perspective. Posts are presumably stored in, and searched from, a database on the server. A search query almost certainly does not actually load a page and all its linked graphical resources just to match a text string, so the performance impact of an image (regardless of size) should be negligible on searches. Similarly, unless some users have aggressive prefetching, simply browsing a board without clicking on a thread is not going produce any additional requests for the the images in that thread. Basically, unless someone is actively loading the page in question, there shouldn't be much more for the server to do. That said, any load on the server from requests for the page will slow down the entire site, not just the page in question. A server is just a computer with finite bandwidth, memory, disk I/O, and processing power; whenever it devotes those resources to a task (like serving a bunch of large, animated GIF images) that comes directly from the pool available for other tasks and users – so a heavy load will affect everything.
If server load from large images has truly been identified as a performance bottleneck, file size limits on uploads really do seem like a useful idea. Implementation is often just a simple setting, not some massive programming task... and it's not that hard to envision similar issues with large images cropping up again every once in a while.
|
|
|
|
