Re: [Openflow-dev] Archiving openflow workitems

[Marco B. <mar...@gm...>]

Hi Danny.

Even though Zope/OpenFlow will not slow down, it will certainly grow
its storage more and more, make it more difficult to manage.

The simplest way is to erase the instances in a batch, using probably
an export. I'm not sure if xml export works, but zexp does.

We've done for a project of us (PAFlow) where we routinely drop old instances.

You can find some example of code in the module InstanceManager.py
which I'm including. This is part of PAFlow, which you can find at:

www.paflow.it
trac.icube.it/trac/PAFlow

sorry, both are in italian.



On 6/8/06, Sinang, Danny <D.S...@sp...> wrote:
>
>
> Hello again,
>
> I think what I really meant was, as we create more processes and workitems,
> will Zope / OpenFlow slow down (because before we assign a job, we ascertain
> it's priority and role first) ?
>
> If so, how do we archive finished tasks / workitems ?
>
> And how do we bring them back in case someone needs to audit them ?
>
> Regards,
> Danny
>
>  ________________________________
>  From: ope...@li...
> [mailto:ope...@li...] On
> Behalf Of Sinang, Danny
> Sent: Wednesday, June 07, 2006 1:51 PM
> To: ope...@li...
> Subject: [Openflow-dev] Archiving openflow catalog contents
>
>
>
> Hello,
>
> As we move more work via OpenFlow, the catalog is surely going to grow.
>
> 1. Will the OpenFlow / Zope server slow down as the catalog grows ?
> 2. If so, how do we archive already-finished processes to make the server
> run faster ?
>
> Regards,
> Danny
>
>
> _______________________________________________
> Openflow-dev mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openflow-dev
>
>
>


-- 
Marco Bizzarri
http://notenotturne.blogspot.com/