Login or Register to Ask a Question and Join Our Community


Complex Event Processing RSS News

On latency in event processing network

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News On latency in event processing network
# 1  
Old 08-05-2008
On latency in event processing network
2008-08-05T09:13:00.005+03:00
Image
Packing, on my way to a family vacation in Anatalya, Turkey.

Following an interesting discussion yesterday about performance metrics -- it turns out that definition of latency in event processing network is quite tricky. The reason is that an event can move in multiple paths over the network, in some it is filterred out, in some it just getting into internal state of agent since it does not complete a pattern, and in some it may complete a pattern and trigger reaction, thus there are various ways to define the metrics here. This is important since optimization has to take into account the goal function - what is being optimized. More discussion on this area -- after I'll return. I'll be out of touch for a week.

Source...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT BSD

lo

LO(4)							     Kernel Interfaces Manual							     LO(4)

NAME

       lo - software loopback network interface

SYNOPSIS

       /sys/conf/SYSTEM:
	    NLOOP     1    # loop-back pseudo-device

DESCRIPTION

       The  loop  interface is a software loopback mechanism which may be used for performance analysis, software testing, and/or local communica-
       tion.  As with other network interfaces, the loopback interface must have network addresses assigned for each address family with which	it
       is to be used.  These addresses may be set or changed with the SIOCSIFADDR ioctl.  The loopback interface should be the last interface con-
       figured, as protocols may use the order of configuration as an indication of priority.  The  loopback  should  never  be  configured  first
       unless no hardware interfaces exist.

DIAGNOSTICS

       lo%d:  can't  handle  af%d.   The  interface  was handed a message with addresses formatted in an unsuitable address family; the packet was
       dropped.

SEE ALSO

       intro(4N), inet(4F), ns(4F)

BUGS

       Previous versions of the system enabled the loopback interface automatically, using a nonstandard Internet address (127.1).   Use  of  that
       address is now discouraged; a reserved host address for the local network should be used instead.

3rd Berkeley Distribution					  August 1, 1987							     LO(4)