Mogar Posted April 26, 2009 Report Share Posted April 26, 2009 wouldn't having 40 per page be better for the server since it means less clicks? Quote Link to comment Share on other sites More sharing options...
thedestro Posted April 26, 2009 Report Share Posted April 26, 2009 That would be true if you couldn't change the settings to whatever you wanted. Quote Link to comment Share on other sites More sharing options...
enderland Posted April 26, 2009 Report Share Posted April 26, 2009 People still have it set to 10? Quote Link to comment Share on other sites More sharing options...
Mogar Posted April 26, 2009 Author Report Share Posted April 26, 2009 People still have it set to 10? No, it changes to 10 by default around update, I noticed this tonight. Quote Link to comment Share on other sites More sharing options...
Delta1212 Posted April 26, 2009 Report Share Posted April 26, 2009 It's to reduce simultaneous database queries. It takes just as many queries to get 40 nations no matter how you split it up, but doing it 10 at a time means you spread it out more. Quote Link to comment Share on other sites More sharing options...
admin Posted April 26, 2009 Report Share Posted April 26, 2009 It's to reduce simultaneous database queries. It takes just as many queries to get 40 nations no matter how you split it up, but doing it 10 at a time means you spread it out more. That's the theory. I'm going to test it for a couple of days to see if it helps any. Quote Link to comment Share on other sites More sharing options...
Lord of the Port Posted April 27, 2009 Report Share Posted April 27, 2009 It depends on what the user wants, I think. If he just wants to see 10 nations, then yes, it will be faster. If the user wants to check a lot of nations at once, then it will be slower though to have everything load by the 10. Explanation: Assume accessing and releasing the database connection are atomic operations, and assume that your query is automagically getting everything sorted in the right order. (You cannot control it anyways, as that part is done in whatever you use to access the database.) Getting 40 nations at once: 1 Access database connection 40 nation queries 1 release database connection. Total: 42 operations Getting 40 nations by the 10: 1 Access database connection 10 database queries 1 release database connection rinse and repeat 3 more times total: 48 operations. However, there is a catch. Assume the process that executes all those queries never gets interrupted for such 'trivial' things as OS stuff. With 40 countries at once, the user hogs the processor for 42 operations, then releases it for another user to use it for his queries. However, if you do 10 countries at once, then the user hogs the processor for 12 operations, then releases it for another user. To make this even more fun, all the operations I described aren't atomic at all. Getting the database access actually takes a while, the queries run relatively fast after that. Taking a value of 2 for the operation of opening the database, and 1 for closing/query, then you are at 43 vs 52. 3: 44 vs 56. etc. My educated guess: limiting it to 10 users in peak-time will increase the number of users that can connect to the site per second, but that is offset by the higher number of times some users will want to visit the site, resulting in a longer peak-time. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.