 | | Re: Member details in set database moved to subpages —Thomas Garrison
|
| | | (...) :-( You know more about LUGNET server load than I do, but is it really that much bandwidth to load some extra text? Not to sound negative. . .but seeing this a few minutes ago just depressed me. The utility of the LUGNET database has just (...) (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | |
| | | | | Re: Member details in set database moved to subpages —Todd Lehman
|
| | | | | (...) The display of the lists on every set lookup was the number two bottleneck in the webserver's CPU load. --Todd (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | | |
| | | | | Re: Member details in set database moved to subpages —Kyle D. Jackson
|
| | | | (...) Back when the personal set data was first introduced to the Guide, Todd and I had discussed that very idea: (URL) to point 3). How about this idea?: If someone is a LUGNET member and are logged into LUGNET, they can toggle a setting that (...) (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: Member details in set database moved to subpages —Todd Lehman
|
| | | | (...) Still leaves a bottleneck, unfortunately. (...) You mean repeating the "My Collection" box in the sub-page(s)? Or glomming the four sub-pages into a single sub-page? --Todd (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | |
| | | | | | Re: Member details in set database moved to subpages —Jennifer L. Boger
|
| | | | | I personally would like the 4 sub pages on a single page. Formatted the way it used to be, just separately. (I actually liked the cookies idea best, so i could have the option, but i'll settle for the above :) ) 4 pages is not "at a glance". (...) (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | | |
| | | | | | | Re: Member details in set database moved to subpages —Larry Pieniazek
|
| | | | | | | (...) I would like to express my preference for this solution as well, with the "my info" part repeated at the top, and maybe with a link to go back (although I'm not clear why the back button isn't good enough for that, it's faster if the page (...) (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | | | | |
| | | | | | | Re: Member details in set database moved to subpages —Todd Lehman
|
| | | | | | (...) I can do that. (...) I'm not sure what you mean here by "used to be" and "separately." (...) Maybe it can swing back to that if I move things to a faster box and if not everyone selects the always-display option. :) --Todd (24 years ago, 7-Mar-01, to lugnet.admin.database)
|
| | | | | | |
| | | | | | | | Re: Member details in set database moved to subpages —Ross Crawford
|
| | | | | | (...) I think maybe "separately" referred to being on a separate page a la new system. And "used to be" may refer to the extra blank lines between comments - I don't remember ever seeing all that white space in the previous incarnation, and I think (...) (24 years ago, 8-Mar-01, to lugnet.admin.database)
|
| | | | | | |
| | | | | | Re: Member details in set database moved to subpages —Kyle D. Jackson
|
| | | | | (...) True, but it helps reduce it. Only logged-in members of LUGNET would see personal data on the Guide pages, and even then only if their preference is toggled to show such. So the question is: of the total hits on the Guide, what percentage come (...) (24 years ago, 8-Mar-01, to lugnet.admin.database)
|
| | | | | |
| | | | | | Re: Member details in set database moved to subpages —Dan Boger
|
| | | | (...) what if we go about it the other way - instead of dynamiclly generating the pages for each hit, regenerate the pages with a rotating list, nice'ed down so it won't be a lot of load... it can check before it starts for a page to see if it needs (...) (24 years ago, 8-Mar-01, to lugnet.admin.database)
|
| | | | |
