Originally posted by Sneeza™:

If I increase the timeout any higher than it currently is, then all of the processes handling requests will start to fill up and cause a backlog. You see, when the process is waiting for data, it's still occupied and can't be used for another request. When all the processes are used, the backlog starts to fill up, which is what happens when you see a website respond really, really slowly to your requests. I'd rather have 90% of the website functioning with 50% of the backpack requests timing out than the website be totally unavailable/ridiculously slow.

Yeah, that makes sense. Thank you

Yeah I was talking about steam servers. I wonder if they do anything to accommodate these sites. I doubt it but it'd be nice.

Yeah, I've also been getting error messages whenever I try to post up a new trade from these large inventories. Please stop making such large changes if the servers can't handle it. They need to pace themselves with this stuff.

My larger inventories won't load so I thought a good fix would be to log out. Then I got a common error:

"Error code: 0x0501 — Steam's OpenID server is currently offline — please try again in a few minutes."

^ not too bothered by that as much as I am with my inventory list because refreshing hasn't been a good fix and obviously logging out isn't gonna help much

UPDATE/OFFICIAL RESPONSE FROM SNEEZA:
If I increase the timeout any higher than it currently is, then all of the processes handling requests will start to fill up and cause a backlog. You see, when the process is waiting for data, it's still occupied and can't be used for another request. When all the processes are used, the backlog starts to fill up, which is what happens when you see a website respond really, really slowly to your requests. I'd rather have 90% of the website functioning with 50% of the backpack requests timing out than the website be totally unavailable/ridiculously slow.