greetings and help! my site is experiencing major slow down. connecting to zope takes more than 5-6 minutes. this happens when i got a lot of users connecting. (apache connection > 250). everything works great if i got < 100 user connections what i've done -upgrade apache to serve more than 256 users by editing httpd.h -up the zope thread from the default to a greater number (100) -added more RAM total = 4G when i connect from the server console, with lynx localhost:8080 , i got a long wait with HTTP request sent; waiting for response. ( about 5-6 minutes for a 20Kb file) if i render the page and let apache serve it, the request is served immedietly. i think this has to do with zope inability to cope with requests. i'm looking at putting squid in front and see what happens. or is it my setting? this is happening on a production server and is very bad. help and pointers to tune zope is apprecieted very VERY much this is zope 2.1.6, on RH with SMP and 4G RAM meanwhile, i'll go bang my head before i look at this again. thanks and help, please! -- ------------------------------------------------------ http://www.kedai.com.my/kk Am I Evil?
I'm curious about the fact that apache can render the page immediately by talking through pcgi/fcgi to ZServer but ZServer can't render the page quickly when you talk to it directy via HTTP. The only reasoning I can see for that is some sort of caching at the browser or in the http server. Have you been able to determine which methods are taking the longest amounts of time? I know you're under pressure to get this solved. I doubt you're going to find a quick solution to this. You may want to take this opportunity to start on the path to 2.2 and ZEO. If you need to solve it fast, get Squid or another caching proxy up in front of it in order to give yourself some breathing room and then start work on 2.2 and ZEO. "Bak @ kedai" wrote:
greetings and help!
my site is experiencing major slow down. connecting to zope takes more than 5-6 minutes. this happens when i got a lot of users connecting. (apache connection > 250). everything works great if i got < 100 user connections
what i've done -upgrade apache to serve more than 256 users by editing httpd.h -up the zope thread from the default to a greater number (100) -added more RAM total = 4G
when i connect from the server console, with lynx localhost:8080 , i got a long wait with
HTTP request sent; waiting for response. ( about 5-6 minutes for a 20Kb file)
if i render the page and let apache serve it, the request is served immedietly. i think this has to do with zope inability to cope with requests. i'm looking at putting squid in front and see what happens. or is it my setting?
this is happening on a production server and is very bad. help and pointers to tune zope is apprecieted very VERY much
this is zope 2.1.6, on RH with SMP and 4G RAM
meanwhile, i'll go bang my head before i look at this again.
thanks and help, please!
-- ------------------------------------------------------ http://www.kedai.com.my/kk Am I Evil?
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Mon, 10 Jul 2000, Chris McDonough wrote:
I'm curious about the fact that apache can render the page immediately by talking through pcgi/fcgi to ZServer but ZServer can't render the page quickly when you talk to it directy via HTTP. The only reasoning I can see for that is some sort of caching at the browser or in the http server. Have you been able to determine which methods are taking the longest amounts of time?
oops. i didn't state that clear enough. i rendered the page fro ZServer and put it in apache. no going through pcgi/fastcgi. just straight apache. what i did: lynx -source http://my.server/ > /home/httpd/html/images_an/
I know you're under pressure to get this solved. I doubt you're going to find a quick solution to this. You may want to take this opportunity to start on the path to 2.2 and ZEO. If you need to solve it fast, get Squid or another caching proxy up in front of it in order to give yourself some breathing room and then start work on 2.2 and ZEO.
i'm cookin here. i'm putting squid in fornt and hope to see something comes out of it. will report soon
participants (2)
-
Bak ＠ kedai -
Chris McDonough