Re: [WebDNA] WebDNA slow processing

This WebDNA talk-list message is from

2011


It keeps the original formatting.
numero = 107722
interpreted = N
texte = I too am getting slammed. WebDNA regularly jumps to 99% and eventually becomes non-responsive. I'm on version 6.x on RedHat. I've been reviewing the .debug file. There are some columns that have data and I'm unsure what the information reflects. It'd sure be great if one of them was response time so I could spot problems, but basically I see lots of search engines pulling the same template with different parameters. Is anyone willing to share a pre-parse and post-parse script combination that would allow me to track response times easily? This could help find the problem/processor consuming requests. Can someone tell me what the columns in the debug file represent, particularly the mysterious numbers and blank fields? For columns, I see date, time, one mysterious number, a second mysterious number, an IP address, a consistently blank column, a template file path, user-agent string, three more consistently blank columns, the document name, the documentroot (or site home directory), URL parameters (everything after the ? in the URL), a blank column, a request header. It's hard to find a problem except that there've been so many requests. Thanks, Bill On Fri, Nov 25, 2011 at 9:53 AM, Thierry Almy wrote: > Daniel > In the WebDNA prefs you can enable the logs, they are stored in the > WebCatalogEngine in your CGI folder. > Thierry > > ______________________ > mac&web gmbh > thierry almy > grabenstrasse 15 > 8200 schaffhausen > switzerland > web www.mac-web.ch > > Am 25.11.2011 um 15:07 schrieb Daniel Meola: > > I am having the same issue on a server with similar specs, but using > CentOS. > Where I can find more information on error reporting for WebDNA (How to t= urn > it on, where the errors report to)? > Thanks, > > Daniel Meola > 301-486-0901 > daniel@knifecenter.com > > > On Fri, Nov 25, 2011 at 8:48 AM, D Brooke wrote: >> >> Hi Thierry, >> Multiple cores will help with multiple requests (processes). It won't >> necessarily help with one request that is having problems. >> >> My suggesting is to turn on the error reporting for WebDNA to see if you >> can correct some of the problems or isolate any issues. Chances are that >> your issue is code related... Either a problem with the code, or a probl= em >> with the efficiency of the code. >> >> D. Brooke Mobile >> >> On Nov 25, 2011, at 7:29 AM, Thierry Almy wrote: >> >> > Hi >> > >> > We're running a copy of WebDNA 6.2 on a MacPro 2x QuadCore 2,4 GHz, 6G= B >> > RAM, OS 10.6.8, iTools 9.0.5i >> > Apache has about 35 vhosts >> > >> > As soon as the server gets a bit load (~100 concurrent connections) an= d >> > WebDNA uses 110% to 160% of the processor, it takes up to 10 seconds t= o >> > serve a page with WebDNA. >> > Since we have 8-Cores in the server, I guess WebDNA should be able to >> > use more than 160% .... or am I wrong? >> > >> > Pages served directly from apache (no DNA) appear very quick. >> > >> > In cases of heavy load I have the following lines in the console log: >> > 25.11.11 14:26:43 =A0 =A0sioux =A0 =A0WebDNA[210] =A0 =A0Error =A0 =A0= Could not >> > establish connection with the module. >> > >> > >> > And I've also seen the following lines, which makes me even more >> > nervous: >> > 25.11.11 11:18:44 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0*** set a breakpoint in malloc_error_break to debug >> > 25.11.11 11:18:45 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0WebCatalog(210,0xa047a540) malloc: *** error for object 0xe0c970: p= ointer >> > being freed was not allocated >> > 25.11.11 11:47:12 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0sem_open failed: returned EMFILE: Too many open files >> > >> > All the lines are repeated several times. >> > >> > >> > How can I find out what's blocking WebCatalog? >> > Is something wrong with my module? >> > >> > >> > Thanks for any help >> > Thierry >> > >> > ______________________ >> > mac&web gmbh >> > thierry almy >> > grabenstrasse 15 >> > 8200 schaffhausen >> > switzerland >> > web =A0 www.mac-web.ch >> > >> > --------------------------------------------------------- >> > This message is sent to you because you are subscribed to >> > the mailing list . >> > To unsubscribe, E-mail to: >> > archives: http://mail.webdna.us/list/talk@webdna.us >> > Bug Reporting: support@webdna.us >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscri= be, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscri= be, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] WebDNA slow processing - conclusion (Kenneth Grome 2011)
  2. Re: [WebDNA] WebDNA slow processing - conclusion (Thierry Almy 2011)
  3. Re: [WebDNA] WebDNA slow processing (Kenneth Grome 2011)
  4. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  5. Re: [WebDNA] WebDNA slow processing (Kenneth Grome 2011)
  6. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  7. Re: [WebDNA] WebDNA slow processing (Kenneth Grome 2011)
  8. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  9. Re: [WebDNA] WebDNA slow processing (Kenneth Grome 2011)
  10. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  11. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  12. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  13. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  14. Re: [WebDNA] WebDNA slow processing (Kenneth Grome 2011)
  15. Re: [WebDNA] WebDNA slow processing (Donovan Brooke 2011)
  16. Re: [WebDNA] WebDNA slow processing ("Mr. Robert Minor Jr." 2011)
  17. Re: [WebDNA] WebDNA slow processing (Donovan Brooke 2011)
  18. Re: [WebDNA] WebDNA slow processing (christophe.billiottet@webdna.us 2011)
  19. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  20. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  21. Re: [WebDNA] WebDNA slow processing (christophe.billiottet@webdna.us 2011)
  22. Re: [WebDNA] WebDNA slow processing ("lists@almy.ch" 2011)
  23. Re: [WebDNA] WebDNA slow processing (christophe.billiottet@webdna.us 2011)
  24. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  25. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  26. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  27. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  28. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  29. Re: [WebDNA] WebDNA slow processing (Donovan Brooke 2011)
  30. Re: [WebDNA] WebDNA slow processing (Donovan Brooke 2011)
  31. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  32. Re: [WebDNA] WebDNA slow processing (William DeVaul 2011)
  33. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  34. Re: [WebDNA] WebDNA slow processing (Thierry Almy 2011)
  35. Re: [WebDNA] WebDNA slow processing (Daniel Meola 2011)
  36. Re: [WebDNA] WebDNA slow processing (D Brooke 2011)
  37. [WebDNA] WebDNA slow processing (Thierry Almy 2011)
I too am getting slammed. WebDNA regularly jumps to 99% and eventually becomes non-responsive. I'm on version 6.x on RedHat. I've been reviewing the .debug file. There are some columns that have data and I'm unsure what the information reflects. It'd sure be great if one of them was response time so I could spot problems, but basically I see lots of search engines pulling the same template with different parameters. Is anyone willing to share a pre-parse and post-parse script combination that would allow me to track response times easily? This could help find the problem/processor consuming requests. Can someone tell me what the columns in the debug file represent, particularly the mysterious numbers and blank fields? For columns, I see date, time, one mysterious number, a second mysterious number, an IP address, a consistently blank column, a template file path, user-agent string, three more consistently blank columns, the document name, the documentroot (or site home directory), URL parameters (everything after the ? in the URL), a blank column, a request header. It's hard to find a problem except that there've been so many requests. Thanks, Bill On Fri, Nov 25, 2011 at 9:53 AM, Thierry Almy wrote: > Daniel > In the WebDNA prefs you can enable the logs, they are stored in the > WebCatalogEngine in your CGI folder. > Thierry > > ______________________ > mac&web gmbh > thierry almy > grabenstrasse 15 > 8200 schaffhausen > switzerland > web www.mac-web.ch > > Am 25.11.2011 um 15:07 schrieb Daniel Meola: > > I am having the same issue on a server with similar specs, but using > CentOS. > Where I can find more information on error reporting for WebDNA (How to t= urn > it on, where the errors report to)? > Thanks, > > Daniel Meola > 301-486-0901 > daniel@knifecenter.com > > > On Fri, Nov 25, 2011 at 8:48 AM, D Brooke wrote: >> >> Hi Thierry, >> Multiple cores will help with multiple requests (processes). It won't >> necessarily help with one request that is having problems. >> >> My suggesting is to turn on the error reporting for WebDNA to see if you >> can correct some of the problems or isolate any issues. Chances are that >> your issue is code related... Either a problem with the code, or a probl= em >> with the efficiency of the code. >> >> D. Brooke Mobile >> >> On Nov 25, 2011, at 7:29 AM, Thierry Almy wrote: >> >> > Hi >> > >> > We're running a copy of WebDNA 6.2 on a MacPro 2x QuadCore 2,4 GHz, 6G= B >> > RAM, OS 10.6.8, iTools 9.0.5i >> > Apache has about 35 vhosts >> > >> > As soon as the server gets a bit load (~100 concurrent connections) an= d >> > WebDNA uses 110% to 160% of the processor, it takes up to 10 seconds t= o >> > serve a page with WebDNA. >> > Since we have 8-Cores in the server, I guess WebDNA should be able to >> > use more than 160% .... or am I wrong? >> > >> > Pages served directly from apache (no DNA) appear very quick. >> > >> > In cases of heavy load I have the following lines in the console log: >> > 25.11.11 14:26:43 =A0 =A0sioux =A0 =A0WebDNA[210] =A0 =A0Error =A0 =A0= Could not >> > establish connection with the module. >> > >> > >> > And I've also seen the following lines, which makes me even more >> > nervous: >> > 25.11.11 11:18:44 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0*** set a breakpoint in malloc_error_break to debug >> > 25.11.11 11:18:45 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0WebCatalog(210,0xa047a540) malloc: *** error for object 0xe0c970: p= ointer >> > being freed was not allocated >> > 25.11.11 11:47:12 =A0 =A0sioux =A0 =A0com.apple.SystemStarter[36] =A0 = =A0Notice >> > =A0sem_open failed: returned EMFILE: Too many open files >> > >> > All the lines are repeated several times. >> > >> > >> > How can I find out what's blocking WebCatalog? >> > Is something wrong with my module? >> > >> > >> > Thanks for any help >> > Thierry >> > >> > ______________________ >> > mac&web gmbh >> > thierry almy >> > grabenstrasse 15 >> > 8200 schaffhausen >> > switzerland >> > web =A0 www.mac-web.ch >> > >> > --------------------------------------------------------- >> > This message is sent to you because you are subscribed to >> > the mailing list . >> > To unsubscribe, E-mail to: >> > archives: http://mail.webdna.us/list/talk@webdna.us >> > Bug Reporting: support@webdna.us >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscri= be, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us > > --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscri= be, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us William DeVaul

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:

WC Database Format (1997) Embedded [Search] Context Snippets (Very Useful) (1998) Multiple database stuff... (1999) Physical Security for WebCatalog Directories (1997) How long does a cart last? (2002) more on quicktime test stuff (1997) (1998) RE: Can a database get stomped by simultaneous access? (1997) [MATH] and Dates (1998) Rendering out a page (1997) Re:Password Authentication - request example (1998) WebCatalog2 Feature Feedback (1996) japanese characters (1997) [listchars] request (was: Bug in capitalize ... ?) (2003) encrypt/decrypt - are docs correct?? (2002) Running 2 two WebCatalog.acgi's (1996) Include a big block of text (1997) Headers displaying (2000) New index for docs (1997) Professional WebDNA Hosting Solutions (2005)