Skip to Content

SWEQADM x System Performance

Hi people,

As you could see by my questions I'm testing a lot of things about performance...

Now, the question is the following: How can the queue be a good way to manage the events that are about thousands per day ?

I know some people have answered to me that using it is the best way to improve system performance.

But I want to know how does it work. Because thinking about it initially, a queue is only a way to put events on sequence and time to time those are triggered. But in the end, the same quantity of events will be triggered as without queue.

What a plus of SWEQADM to really improve the system performance ?

Here we have (only counting the events marked to use queue) from 55 per minute up to 195 events per minute depending what time of the day.

Does anybody know ?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jan 04, 2007 at 02:48 PM

    Hi,

    As you rightly say, the number of events plus the performance needed won't lessen when you use the event queue, in fact it will go up.

    The event queue is used to even out the performance, this means, in theory, that users will have less inconvenience about response times when all of a sudden thousands of events get triggered.

    If it is important for the system to balance the performance, the event queue is definately a solution worth considering.

    I have seen cases where the event queue was switched off because it used too much resources, instead we came up with various solution in which most of the events were triggered at nighttimes, or in the weekend.

    Kind regards, Rob Dielemans

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 04, 2007 at 02:50 PM

    Hi Glauco,

    From the help:

    <i>You can use the event queue to delay the starting of receivers reacting to a triggering event. To achieve this, the receivers are stored in a temporary memory.</i>

    and

    <i>This means that the system load caused by a large number of events being created can be spread over a longer time period (which can be set by the workflow system administrator). This combats the threat of system overload</i>

    A perfect answer to your question, if there's something you don't understand we're glad to help.

    Another tip: Also look at the help for the latest versions. Sure, things may work differently but often some of the basics are also explained better.

    Cheers,

    Mike

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.