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 turn it on, where the errors report = to)?
On Fri, Nov 25, 2011 at 8:48 AM, D = Brooke <dbrooke@euca.us> = 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 = problem with the efficiency of the code.
D. Brooke Mobile
On Nov 25, 2011, at 7:29 AM, Thierry Almy <lists@almy.ch> wrote:
> Hi
>
> We're running a copy of WebDNA 6.2 on a MacPro 2x QuadCore 2,4 GHz, = 6GB 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) = and WebDNA uses 110% to 160% of the processor, it takes up to 10 seconds = to 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 sioux WebDNA[210] = Error 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 sioux = com.apple.SystemStarter[36] Notice *** = set a breakpoint in malloc_error_break to debug
> 25.11.11 11:18:45 sioux = com.apple.SystemStarter[36] Notice = WebCatalog(210,0xa047a540) malloc: *** error for object 0xe0c970: = pointer being freed was not allocated
> 25.11.11 11:47:12 sioux = com.apple.SystemStarter[36] Notice = sem_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 www.mac-web.ch
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> 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 <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
______________________ mac&web gmbh thierry almy grabenstrasse 15 8200 schaffhausen switzerland web www.mac-web.ch
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 turn it on, where the errors report = to)?
On Fri, Nov 25, 2011 at 8:48 AM, D = Brooke <dbrooke@euca.us> = 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 = problem with the efficiency of the code.
D. Brooke Mobile
On Nov 25, 2011, at 7:29 AM, Thierry Almy <lists@almy.ch> wrote:
> Hi
>
> We're running a copy of WebDNA 6.2 on a MacPro 2x QuadCore 2,4 GHz, = 6GB 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) = and WebDNA uses 110% to 160% of the processor, it takes up to 10 seconds = to 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 sioux WebDNA[210] = Error 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 sioux = com.apple.SystemStarter[36] Notice *** = set a breakpoint in malloc_error_break to debug
> 25.11.11 11:18:45 sioux = com.apple.SystemStarter[36] Notice = WebCatalog(210,0xa047a540) malloc: *** error for object 0xe0c970: = pointer being freed was not allocated
> 25.11.11 11:47:12 sioux = com.apple.SystemStarter[36] Notice = sem_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 www.mac-web.ch
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us>.
> To unsubscribe, E-mail to: <talk-leave@webdna.us>
> 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 <talk@webdna.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us
DOWNLOAD WEBDNA NOW!
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...