Re: Webcat XML/XSLT Performance vs. static Html
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66250
interpreted = N
texte = Regarding products there are well over 30k, and products is one of several portions of the site accessed daily by over 12k users, who probably access these detail pages over and over while using the site. We have noticed similar sites in this vertical market use a dynamic technology like webcat to serve static html pages - this is giving them very fast page loads under heavy traffic loads - obviously because there is little to process if anything. Although we could rewire our detail pages, 'programmatically' speaking, our goal is to serve these detail pages without having to create db connections. My idea is to create a small xml file everytime a user adds a product and/or re-write this xml file anytime a modification has taken place. Therefore, the xml file would mirror what is in the db. So when a user clicks to see a product's details from the results page, they would be served a static page - therefore not needing to access our SQL sever. In order to keep this manageable as possible, I would like to use one xsl file to display these xml files, via webcat's xslt function. Therefore, I would have 30k+ xml files and 1 xsl file. The details page would have one like of script, a script that grabs the xml file and merges it with the xsl file. This why I am wondering how resource intense webcat's xml/xsl features. I know it wouldn't be a big deal on a small/medium scale, but are situation is larger. Donovan Brooke wrote: > Adam O'Connor wrote: > >> Has anyone noticed any performance issues with webcat's XML/XSL >> features? >> >> We are going to be replacing our detail pages with static pages. Our >> details pages are taking up too many resources due to embedded >> searches and misc db connections. etc. Therefore we are going to >> change our methodology and use static pages for our details page. >> Because of this we are wondering which would be fastest and most >> dependable, static html files or xml files parsed and displayed by >> webcat. >> >> I would like to use xml, but I don't want to be back where we >> started, having performance issues due to webcat having to parse an >> xml file everytime a details page is displayed. However, the xml >> will be a small file. >> So is parsing an xml file about the same as doing an [include file], >> from a resource perspective, or is it more resource intense? >> >> Any comments? > > Adam, you must have a lot of products, or a slow machine to have > performance > issues. And, if you do have a lot of products, doing static html pages > for > the details seems mind boggling. I would go over the code and see if it > can be written more lean and mean so to speak. > > Donovan > > > Oh, I've only done shipping API's with xml but they work quickly and > seem dependable so far. > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Regarding products there are well over 30k, and products is one of several portions of the site accessed daily by over 12k users, who probably access these detail pages over and over while using the site. We have noticed similar sites in this vertical market use a dynamic technology like webcat to serve static html pages - this is giving them very fast page loads under heavy traffic loads - obviously because there is little to process if anything. Although we could rewire our detail pages, 'programmatically' speaking, our goal is to serve these detail pages without having to create db connections. My idea is to create a small xml file everytime a user adds a product and/or re-write this xml file anytime a modification has taken place. Therefore, the xml file would mirror what is in the db. So when a user clicks to see a product's details from the results page, they would be served a static page - therefore not needing to access our SQL sever. In order to keep this manageable as possible, I would like to use one xsl file to display these xml files, via webcat's xslt function. Therefore, I would have 30k+ xml files and 1 xsl file. The details page would have one like of script, a script that grabs the xml file and merges it with the xsl file. This why I am wondering how resource intense webcat's xml/xsl features. I know it wouldn't be a big deal on a small/medium scale, but are situation is larger. Donovan Brooke wrote: > Adam O'Connor wrote: > >> Has anyone noticed any performance issues with webcat's XML/XSL >> features? >> >> We are going to be replacing our detail pages with static pages. Our >> details pages are taking up too many resources due to embedded >> searches and misc db connections. etc. Therefore we are going to >> change our methodology and use static pages for our details page. >> Because of this we are wondering which would be fastest and most >> dependable, static html files or xml files parsed and displayed by >> webcat. >> >> I would like to use xml, but I don't want to be back where we >> started, having performance issues due to webcat having to parse an >> xml file everytime a details page is displayed. However, the xml >> will be a small file. >> So is parsing an xml file about the same as doing an [include file], >> from a resource perspective, or is it more resource intense? >> >> Any comments? > > Adam, you must have a lot of products, or a slow machine to have > performance > issues. And, if you do have a lot of products, doing static html pages > for > the details seems mind boggling. I would go over the code and see if it > can be written more lean and mean so to speak. > > Donovan > > > Oh, I've only done shipping API's with xml but they work quickly and > seem dependable so far. > > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Adam O'Connor
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[WebDNA] Syntax Error? (2009)
[ShowNext] feature in 2.0 (1997)
RE: OK, here goes... (1997)
read and write you own cookies with webcat (1997)
6.0 Upgrade Issue (2005)
WebCat2 several catalogs? (1997)
encrypt but with normal characters for result? (2005)
Q: writefile and uploads. (1998)
Sorting alphabetical (2003)
Showif date range comparison (1999)
Searchable list archive (1997)
absolute paths for databases? (1997)
[Announce]: Web server security and password protection (1997)
HUGE DATABASES (1998)
WebCommerce: Folder organization ? (1997)
Including encrypted templates ... ? (2003)
lookup and two records? (1997)
Extended [ConvertChars] (1997)
normal users.db calls ... (1998)
2 Nt's (1998)