Re: Performance Tuning
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66500
interpreted = N
texte = Thanks, John. You always seem to respond to my posts with helpful advice. I'm determining that webdna is maxing out the cpu by watching the activity monitor on OSX. the webdna process is spiking at 100% while the webstar webserver process is at a much smaller amount that typically stays under 50%. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of John Peacock Sent: Friday, March 24, 2006 1:49 PM To: WebDNA Talk Subject: Re: Performance Tuning Allen Frye wrote: > I'm having some issues with WebDNA maxing out the cpu and I could use > some help tuning webdna. We run webdna 5 on OSX with webstar, dual 1.3 > machine with 4gigs of ram, primarily for one site. Last month we > received 24 million page views, about 1.5 million visitor sessions, > and 300 visitors per hour. You need to realize that the site design is probably at least as important (if not more so) as server tuning. How are you determining that WebDNA is maxing out the CPU and not WebStar? Can you use your server logs to see which page is being viewed most often? Is this a fully dynamic site (where each page is mostly served out of the DB's) or a most static site (where pages have some dynamic content, but most of the processing is serving up static content)? You need to get a good idea for how much CPU is spent rendering the page and how much is spent searching the DB's. One way to do this is to take some subsection of your site and pre-render the pages to fully static content and then see how that affects your overall processing time. > We're in the process of migrating to MySQL and > PHP, but in the meantime any ideas would be appreciated. Don't expect that to automatically be faster, taking into consideration the above discussion. On a page-per-page basis, a RAM resident database is always going to beat a disk-bound database, no matter how slow the RAM searching is (disks are milliseconds and RAM is nanoseconds). John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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:
Thanks, John. You always seem to respond to my posts with helpful advice. I'm determining that webdna is maxing out the cpu by watching the activity monitor on OSX. the webdna process is spiking at 100% while the webstar webserver process is at a much smaller amount that typically stays under 50%. -----Original Message----- From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com] On Behalf Of John Peacock Sent: Friday, March 24, 2006 1:49 PM To: WebDNA Talk Subject: Re: Performance Tuning Allen Frye wrote: > I'm having some issues with WebDNA maxing out the cpu and I could use > some help tuning webdna. We run webdna 5 on OSX with webstar, dual 1.3 > machine with 4gigs of ram, primarily for one site. Last month we > received 24 million page views, about 1.5 million visitor sessions, > and 300 visitors per hour. You need to realize that the site design is probably at least as important (if not more so) as server tuning. How are you determining that WebDNA is maxing out the CPU and not WebStar? Can you use your server logs to see which page is being viewed most often? Is this a fully dynamic site (where each page is mostly served out of the DB's) or a most static site (where pages have some dynamic content, but most of the processing is serving up static content)? You need to get a good idea for how much CPU is spent rendering the page and how much is spent searching the DB's. One way to do this is to take some subsection of your site and pre-render the pages to fully static content and then see how that affects your overall processing time. > We're in the process of migrating to MySQL and > PHP, but in the meantime any ideas would be appreciated. Don't expect that to automatically be faster, taking into consideration the above discussion. On a page-per-page basis, a RAM resident database is always going to beat a disk-bound database, no matter how slow the RAM searching is (disks are milliseconds and RAM is nanoseconds). John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4501 Forbes Boulevard Suite H Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5748 ------------------------------------------------------------- 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/ ------------------------------------------------------------- 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/
"Allen Frye"
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:
[append] problem (1997)
Shopping Cart Directory (2000)
WebCat2b15MacPlugIn - [authenticate] not [protect] (1997)
taxRate is fine but taxTotal isn't (1997)
expansion domain freak out (2003)
Grant, please help me ... (1997)
No Subject (1998)
Odd request (2003)
createfolder permissions (2003)
Duplicates (1998)
Security (1998)
Searching multiple fields from one form field (1997)
WebCat2 - [include] tags (1997)
Installation webCatalog (French speakers please help) (1998)
[ot] Webserver monitoring (2001)
WebDNA Quick Reference (Reserved Words) (2000)
Expiration of Carts (1997)
Emailer problem (1998)
Help with update to 2.11 (1998)
Nested vs conditional (1997)