Re: [Zope] Zope 2.9 Product Refreshing
On 8/7/06, Andreas Jung <[EMAIL PROTECTED]> wrote: You might blame Plone for shipping for three tons of frameworks?Incidently, I've just added some print statements to trace the Zope startup, and "Five" is by far the slowest product to load, taking about 3 seconds. Running up is PlacelessTranslationService at around 1.5 seconds (And much less if I kill all .po files). -James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On Tuesday 08 August 2006 01:34, you wrote: > You mean you can't allow the server even to be down for the less than > a minute it takes to restart it? I would honestly be very interested > in knowing what kind of systems you run that has that sort of > requirements. Are you serious? People pay large sums of money for us to host there critical business infrastructure. If we have to restart zope for any reason, people get apache proxy errors and lose session data. -James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
This isn't really a solution. Clients will still lose session data, which is unacceptable. -James. On Monday 07 August 2006 22:15, Reinoud van Leeuwen wrote: > On Mon, Aug 07, 2006 at 10:12:42PM +1000, James Davies wrote: > > We have Zeo, but running a seperate instance of zope for each site is > > still too much (We probably host around 50 sites at the moment, and > > growing. The only economical way to do this is to put multiple sites in > > one zope instance). > > Still you can shutdown 1 ZEO client; update products there and start it up > again... There will be some performance degradation but the sites stay > up... (and I hope you've got enough ZEO clients so that bringing 1 down > will not cause severe problems...) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
We have Zeo, but running a seperate instance of zope for each site is still too much (We probably host around 50 sites at the moment, and growing. The only economical way to do this is to put multiple sites in one zope instance).On 8/7/06, Reinoud van Leeuwen <[EMAIL PROTECTED]> wrote: On Mon, Aug 07, 2006 at 09:47:37PM +1000, James Davies wrote:> Another major issue I've discovered is Zope hosting. We reguarly deploy> custom sites on shared zope environments, and having to restart an entire > server just to update one product severely breaks our uptime guarentee.If you use a ZEO setup you can restart the ZEO clients one-by-one. Worksfor me without downtime...--__ "Nothing is as subjective as reality"Reinoud van Leeuwen[EMAIL PROTECTED]http://www.xs4all.nl/~reinoud _Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope** No cross posts or HTML encoding! **(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zope 2.9 Product Refreshing
On 8/7/06, Andreas Jung <[EMAIL PROTECTED]> wrote: Refreshing was always a hack and never something I would call a feature.It was always a hack for *development* purposes but not for production. Yes, but it's still very handy and many people have come to rely on it. You might blame Plone for shipping for three tons of frameworks? I'd agree with you there- theres a little too much bloat, but theres not much that can be done about it at this point without a major architecture update. I understand and fully agree with you but things are as they are. EvenworserRefresh does not work Five... How come? Is there a major technical reason why it CANT work, or is it something thats just broken and needs fixing. I'm happy to do the fixing if it comes to that, I just need someone to point me in the right direction. Refresh only works in debug-mode. You want to tell us that you are runninga production site in debug-mode? No. I've never had a problem refreshing in production mode ? Dieter Maurer wrote a RefreshTool product lately (not sure if this wouldsolve your problem and not sure if he released it). I'll have a look- thanks. I doubt that the Refresh situation will change in the near future. As above- is this a major technical problem with Zope 2.9 or Five, or just something that no-one is really bothered to fix? Thanks, James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope 2.9 Product Refreshing
Hi. I've been attempting to develop products with Zope 2.9, and am finding it increasingly difficult and slow to do so as Product refreshing no longer works. Google shows up a few results from mailing lists with somewhat negative responses (The gist I'm getting is that no-one 'in the know' wants to worry about fixing it, as they don't see a real need for it). However, as a zope restart seems to take a good 5-10 seconds on my high end workstation (AthlonX2 4800+) with all the essentiall products installed (Plone, archetypes etc, plus my application), it's starting to become a major problem. as an example, I spent about three hours today debugging a problem, 90% of which was wasted waiting for zope restarts after making small changes and adding trace print statements. If I was able to refresh the product I would likely have taken less than half an hour. Another major issue I've discovered is Zope hosting. We reguarly deploy custom sites on shared zope environments, and having to restart an entire server just to update one product severely breaks our uptime guarentee. I'm afraid we are going to have no choice but to either drop back to Zope 2.8, or ditch Zope entirely- something I'd prefer not to have to do with our large codebase. I'm hoping I can garner some support to get the zope developers to fix the problem. Failing that, ANY information pointing me in the right direction would be helpful, as I'm more than happy to fix it myself and submit a patch. If anyone else is finding this a problem, please reply in this thread. :-) Thanks in advance. James. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
