Re: [Hypercontent-users] Workflow Screen Load Performance

[Alex V. <al...@bi...>]

Hey Adam,
That is possible, although not trivial to implement (there are lots  
of queues involved - in each project, there's one per each "q" in  
each workflow script plus one per user - you'd have to make sure to  
delete each work item from each of it's queues and delete the work  
item itself).

An other approach would be to tweak the workflow scripts themselves,  
e.g. in publish.xml

<q id="published">
		<event name="batch-reset">
			<dq/>
			<nq q="publishing"/>
		</event>
		<event name="discard" who="${publisher}">
			<dq/>
			<dq who="${publisher}"/>
		</event>
		<event name="auto-discard" when="in 30 days">
			<dq/>
			<dq who="${publisher}"/>
		</event>
	</q>

Notice the last event just has a schedule set on it, and dequeues  
from all active queues, which will also trigger the work data to be  
discarded.

Alex

On Apr 29, 2008, at 3:07 PM, Adam Carl wrote:

> Alex,
>
> Does this seem possible?
>
> 1) Create a workflow script in the bootstap project that gets  
> executed daily
> (late at night) which calls a custom command object
> 2) The command object would ideally rotate through each project and  
> clean
> one project per day.  (Remove workflow files which are older than  
> 30 days)
>
> Adam
>
>
>
>
> On 4/25/08 4:43 PM, "al...@bi..." <al...@bi...> wrote:
>
>> Hey Adam,
>> The latest build won't help with this issue.  The problem is mostly
>> due to the way the workflow details screen loads data for all tasks
>> related to a given script.  Improving the performance would primarily
>> involve re-writing the workflow screens to use AJAX to load just the
>> data needed to construct the current view.  The best short-term  
>> advice
>> I can give is to tweak scripts so that they automatically delete
>> completed tasks after a window of time, so that you don't get such a
>> large history of tasks built up on those screens.
>>
>> Alex
>>
>> Quoting Adam Carl <ac...@co...>:
>>
>>> Alex,
>>>
>>> At Columbia we have noticed the Workflow tab can take a fair  
>>> amount of time
>>> to load for certain people and certain projects.    If we shut down
>>> Hypercontent and delete the workflow-data folder for a project the
>>> performance is improved.
>>>
>>> Any suggestions?  Our build of Hypercontent in production is over  
>>> a year
>>> old, we are testing the latest code in CVS now and will be  
>>> promoting that
>>> next week.   Should that help with this problem?
>>>
>>> Thanks,
>>>
>>> Adam
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -----
>>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>>> Don't miss this year's exciting event. There's still time to save  
>>> $100.
>>> Use priority code J8TL2D2.
>>>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// 
> java.sun.com/javaon>>
> e
>>> _______________________________________________
>>> Hypercontent-users mailing list
>>> Hyp...@li...
>>> https://lists.sourceforge.net/lists/listinfo/hypercontent-users
>>>
>>
>>
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>> Don't miss this year's exciting event. There's still time to save  
>> $100.
>> Use priority code J8TL2D2.
>> http://ad.doubleclick.net/clk;198757673;13503038;p?http:// 
>> java.sun.com/javaone
>> _______________________________________________
>> Hypercontent-users mailing list
>> Hyp...@li...
>> https://lists.sourceforge.net/lists/listinfo/hypercontent-users
>