increase the max threads per page?

[ShadowAvatar]

I always browse on very high speed connections with big monitors, and find 100 threads per page a bit small. I would imagine the better majority of the vastly technical people using this site are not on modems anymore, either.

Also, since every page loaded likely spawns 6 GET's under HTTP 1.1 (mine's hacked to be much higher), the net effect of the change should be to lower the consumed bandwith and raise the thruput on each connection. Would this be ameniable to both server and client?

You may get fewer bumps in the FS/T forums, since more people would be visible on the "first page".

 

[ProviaFan]

You have to remember that although the "technical" users here who have broadband significantly outnumber the number of "technical" users who have dialup (I'm unfortunately included in the latter group), the number of people who browse on 22 inch monitors at 2048x1536 resolution are quite few. Therefore, I don't think it would save much bandwidth, although if it's just a matter of changing a #define in a header file for FuseTalk, Zuni might consider changing it.

 

[ShadowAvatar]

Yeah, I understand. I'm actually running dual 21's on my g450 for a grand total of 2560x2048

If it's just a tweak, maybe that would be good. Can always change it back if it's no good.

 

[Scootin159]

I think it's there more to save the servers & bandwidth than it has to do with download times. It's customizeable so that if you have a modem you can knock it down to 20 or so, but capped @ 100 so that everyone doesn't set it to 1000 or something like that & kill the servers. Plus 100 thread is a LOT, you can just hit the next button if ya need to.

 

[Jason Clark]

100 is plenty, we won't change that. The setting isn't just for users, queries are tailored to those values as well. Thanks