about
search
post article
Documentation
Mailing Lists
Bug Tracking
Development
Installation
Upgrading
Download
admin
rdf
main
parent
|
Re: Slow Server
by on Friday February 25, 11:09PM, 2000
|
is this hurrah.com by chance? not to pick on them.. David does a great job - but the boxes crawl sometimes. I'm hosting a site there.. but their boxes arent the fastest beasts.. its called SLOWlaris for a reason :)
I can promise you its the processing on the boxes. this is NOT A problem (at work I run squishdot for intranet discussion perfect use btw) w/ Zope or Squishdot. what I DO have a problem w/ is the instability of ZServer. Its not as mature as apache (yes sure sure technocrat.net has been slashdotted) but when I have multiple browsers beating on Zserver all day ( some ppl waiting for the entire request, some ppl stopping the request, .. true chaos) it usually crashes within 24/48 hours :( -- I have been told ZServer is mature (but to think its even close to apache is a pipe-dream)
my suggestion: ssh into your zope-aware ISP and do a top and see whats eating all the processing (scheudler?).. and if it doesnt get better contact me and I can point you to a ISP that hosts Zope (but not advertised yet)..
runyaga
|
|
 Related Links
|
|
|
|
The Fine Print: The following comments are owned by whoever posted them.
( Reply )
|
Re: Slow Server
by on Saturday February 26, 08:14PM, 2000
|
I've found the Zope/Medusa combination to work
really well for our internal tech support/FAQ
site, which runs Squishdot for the main page. Of
course, we only run a few hundred hits a day on a
dual PPRO 180 machine w/192 MB RAM.
We do it the way described below because it's
important to keep various Zope databases on the
same machine completely separated.
We've noticed it keeps database sizes very
reasonable and access times low running multiple
Zservers.
However, I've not seen anywhere else the method
I've used to talk to the server using mod_rewrite.
We run one of the Zservers on port 8080, and
have a rewrite rule like this in the
VirtualHost directive (doing it from memory,
forgive me if your mileage varies):
RewriteRule ^/docs(.*)$ http://localhost:8080/squishdot/ [P]
This approach allows the Apache server, instead
of using CGI to handle requests, to internally
proxy requests and then deliver them to
the end-user. So far we've had no problems, and
users have been quite happy with the system --
particularly not needing to share their Zserver with anyone else.
Now, how to stop the users from using the wrong port
for their Zserver is always a pain, but most
like for it to actually work and don't
want to hack around Zope too much...
We have multiple Zope installs each with it's own
database in the home directories of the
users. Anyone else using a similar approach, or is this entirely non-scalable?
Good luck with your performance problems!
Matthew P. Barnson
Mgr, Systems Administration
Excite@Home E-Business Services
|
[ Reply to this ]
|
Re: Slow Server
by on Tuesday February 29, 03:30PM, 2000
|
I'm interested in using Zope and Squishdot, but I found the message about ZServer's immaturity disturbing.
I'd be very interested in hearing other feedback about the stability of the software!
Gary
|
[ Reply to this ]
|
-
Re: Slow Server
by on Friday March 03, 02:30AM, 2000
|
ZServer is nice - just as long as you put apache in front of it everything plays well and is rock solid. and for development ZServer can be run solo. in production - Apache w/ FastCGI is the only acceptable solution (for large production environments); on our intranet (where I'm using squishdot) Apache w/ PCGI is fine < 1000 hits/day.
HTH,
runyaga
|
[ Reply to this ]
|
|
The Fine Print: The following comments are owned by whoever posted them.
( Reply )
|
|
