[Erp5-dev] [Erp5-report] r42287 nicolas.dumazet - /erp5/trunk/buildout/instance-profiles/zope-2.12.cfg
Kazuhiko Shiozaki
kazuhiko at nexedi.com
Thu Jan 13 07:56:24 CET 2011
On 13/01/2011 07:34, nobody at svn.erp5.org wrote:
> Author: nicolas.dumazet
> Date: Thu Jan 13 07:34:11 2011
> New Revision: 42287
>
> URL: http://svn.erp5.org?rev=42287&view=rev
> Log:
> for zope 2.12 timer-server has been renamed into clock-server
No!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Please see mypost "Re: [Nexedi] activity invoking seems slower in
Zope-2.12" in nexedi ML on Jan 02.
Or is it intentionall after reading it?
> Hello,
>
> On 02/11/2010 06:23, Yoshinori Okuji wrote:
>> > There is no reason to stick to ClockServer. I guess that ClockServer was
>> > adopted, only because I wrote an article on the wiki wihch mentioned using
>> > ClockServer, when I was trying to port ERP5 to Zope 2.10. I did so, simply
>> > because ClockServer got bundled with Zope2, and didn't want to spend time on
>> > porting TimerService at that time.
> I modified timerserver (released as 2.0.1) so that it works on Zope-2.12
> too. Now you can use timerserver in Zope-2.12 just same as Zope-2.8 by
> adding the following in zope.conf:
>
> # Timerserver to have ticks in zope
> %import timerserver
> <timer-server>
> interval 5
> </timer-server>
>
> The benefits of using timerserver instead of ClockServer are:
> * activities will be invoked more often than every 30 seconds of
> ClockServer.
> * no longer tons of /Control_Panel/timer_service/... in Z2.log.
>
> Enjoy.
>
>> > On Thursday 28 October 2010 11:04:56 pm Robin Sébastien wrote:
>>> >> Hello,
>>> >>
>>> >> I checked further, the 30 second is coming from the default setting of 30
>>> >> seconds in the asyncore.loop call in
>>> >> Zope2-2.12.9-py2.6-linux-x86_64.egg/LifeTime/__init__.py
>>> >>
>>> >> So it looks like that ClockServer is not able to manage anything that
>>> >> happens more often than every 30 seconds with default values.
>>> >>
>>> >> Some thinking will be needed in order to know how to fix it in a nice way.
>>> >>
>>> >> Seb.
>>> >>
>>> >> On 28/10/10 15:05, Kazuhiko Shiozaki wrote:
>>>> >>> Hello,
>>>> >>>
>>>> >>> After switching to Zope-2.12, I feel that activity invoking is slower
>>>> >>> than before, eg. an activity is invoked about 30 seconds after it is
>>>> >>> queued.
>>>> >>>
>>>> >>> Séb also has such impression. Do you have any idea?
>>>> >>>
>>>> >>> In zope.conf, it is written like:
>>>> >>>
>>>> >>> <clock-server>
>>>> >>> method /Control_Panel/timer_service/process_timer?interval:int=5
>>>> >>> period 5
>>>> >>> </clock-server>
>>>> >>>
>>>> >>> BTW, Z2.log add the following line every 30 seconds,
>>>> >>> "GET /Control_Panel/timer_service/process_timer%3Finterval%3Aint%3D5 ..."
>>>> >>> We don't have such lines in Zope-2.8 and I feel that it is also
>>>> >>> annoying...
> -- Kazuhiko Shiozaki, Nexedi SA Senior Consultant Nexedi: Consulting and Development of Free / Open Source Software http://www.nexedi.com ERP5: Full Featured High End Open Source ERP http://www.erp5.com ERP5 Wiki: Developer Zone for ERP5 Community http://www.erp5.org _______________________________________________ Nexedi mailing list Nexedi at erp5.org https://mail.tiolive.com/mailman/listinfo/nexedi
--
Kazuhiko Shiozaki, Nexedi SA Senior Consultant
Nexedi: Consulting and Development of Free / Open Source Software
http://www.nexedi.com
ERP5: Full Featured High End Open Source ERP
http://www.erp5.com
ERP5 Wiki: Developer Zone for ERP5 Community
http://www.erp5.org
More information about the Erp5-dev
mailing list