Bandwidth issues on the main site

[Ngreth Thergn]

Oh MY...

I forgot how horribly complex the code that makes that area is...

it may take a while for me to figure out how to unravel it and put anything like that in...

[KyrosKrane]

Heh. One of these days I'd like to take a look at the actual code that runs this site. I think it would be a real eye-opener.

Anywho, good luck, and holler if you need a hand.

[Ngreth Thergn]

Ok Code is now in for that, and set for Celestial Essense... Now we jsut need to decide what gets marked as such

[Sanna]

/agree Kryos. The small code-monkey part of me finds that fascinating. (I've never had to run a large site where much is automated, all the ones I've done have been muuuch smaller... I can't even imagine what it takes to do something like EQTC, but it would be fascinating to know.)




If the question is not rhetorical and inputting a copper or two is ok...

-- Anything to do with [any kind of] Ore or Rusty/Tarnished/FS weapon conversions.
-- Egg-type recipes (Noodles, Dough, where you have 15+ recipies that make the same finished Item).
-- Anything where it's easier AND cheaper to buy from a vendor, than to make*; Bread comes to mind, as do brewing things like Short Beer and Elvish Wine. Sure you can /make/ Elvish Wine, but no one in their right mind will spend the Morning Dews for it.


-- Sanna
hoping she hasn't missed a cue again >_< but the idea is great; every little bit somewhere will add up.


* I know this gets a little... nitpicky? not to mention that since I have no idea /HOW/ this code is going to have to be tagged to each item/combine, that may not be imaginably feasable.

[mikebridge]

perhaps using cookies to add 'recently viewed recipes' under the primary menu list on the left would end up with an overall decrease in the bandwidth? (haven't seen the weblogs to see if there are trends in pageviews, i.e. frontpage, search, recipe over and over to same recipe).

also, are the pages dynamically created every request, or do you statically generated the recipes every X minutes/hours to reduce CPU/database hits? the only thing that i see that should be dynamic is the search, the rest could easily be scripted out to static pages....

[Ngreth Thergn]

Originally posted by mikebridge
perhaps using cookies to add 'recently viewed recipes' under the primary menu list on the left would end up with an overall decrease in the bandwidth? (haven't seen the weblogs to see if there are trends in pageviews, i.e. frontpage, search, recipe over and over to same recipe).

not sure this would be a huge help... but the logs don;t generate much help

also, are the pages dynamically created every request, or do you statically generated the recipes every X minutes/hours to reduce CPU/database hits? the only thing that i see that should be dynamic is the search, the rest could easily be scripted out to static pages....

it is dynamic... just items alone would be >10000 pages created. I know it is posible... but it would take a major redesign of how the site works.

[mikebridge]

actually, now that i think about it, you could add about 20 lines of code + 1 database field to do this (depending on how you have the generation setup)
add a 'last mint timestamp' field onto the items/recipes in the database, then when a page is requested, check the stamp, if its been > than XX time since that stamp, have the output of the page generation dump to a standardized filename like item.ITEMID (instead of it being sent to client), then just pipe the contents of that file as the 'body' of the request html page. if the XX time hasn't come up yet, then just pipe them the contents of the text file as the body of the page....

[KyrosKrane]

This would reduce the load on the database server somewhat, but to my understanding, that hasn't been an issue (barring some mistakes like infinite recursion). The problem in general appears to be bandwidth consumption by data transferred to the clients. While static page generation would help server load, it would have no effect on data transmitted to end users as either way, the same page is getting sent.