1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<!--Converted with LaTeX2HTML 2002-2-1 (1.71)
original version by: Nikos Drakos, CBLU, University of Leeds
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
* with significant contributions from:
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
<HTML>
<HEAD>
<TITLE>Ergebnis</TITLE>
<META NAME="description" CONTENT="Ergebnis">
<META NAME="keywords" CONTENT="diplomathesis">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<META NAME="Generator" CONTENT="LaTeX2HTML v2002-2-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="diplomathesis.css">
<LINK REL="previous" HREF="node61.html">
<LINK REL="up" HREF="node61.html">
<LINK REL="next" HREF="node63.html">
</HEAD>
<BODY >
<DIV CLASS="navigation"><!--Navigation Panel-->
<A NAME="tex2html1025"
HREF="node63.html">
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
SRC="/usr/share/latex2html/icons/next.png"></A>
<A NAME="tex2html1021"
HREF="node61.html">
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
SRC="/usr/share/latex2html/icons/up.png"></A>
<A NAME="tex2html1017"
HREF="node61.html">
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
SRC="/usr/share/latex2html/icons/prev.png"></A>
<A NAME="tex2html1023"
HREF="node3.html">
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents"
SRC="/usr/share/latex2html/icons/contents.png"></A>
<BR>
<B> Next:</B> <A NAME="tex2html1026"
HREF="node63.html">V4 Scheduling</A>
<B> Up:</B> <A NAME="tex2html1022"
HREF="node61.html">V3 Verhalten bei größeren</A>
<B> Previous:</B> <A NAME="tex2html1018"
HREF="node61.html">V3 Verhalten bei größeren</A>
<B> <A NAME="tex2html1024"
HREF="node3.html">Contents</A></B>
<BR>
<BR></DIV>
<!--End of Navigation Panel-->
<H4><A NAME="SECTION00063510000000000000">
Ergebnis</A>
</H4>
<P>
<DIV ALIGN="CENTER">
<P><A NAME="img:2Consumer"></A><A NAME="img:dataLat"></A></P>
<DIV ALIGN="CENTER">
</DIV><TABLE WIDTH="340"><CAPTION ALIGN="BOTTOM"><STRONG>Figure 24:</STRONG>
RT EventService mit 2 Consumern</CAPTION>
<TR><TD>
[width=]./img/v2-2Consumer.jpg
</TD></TR>
</TABLE>
<DIV ALIGN="CENTER">
</DIV>
<DIV ALIGN="CENTER">
</DIV><TABLE WIDTH="340"><CAPTION ALIGN="BOTTOM"><STRONG>Figure 25:</STRONG>
Abhängigkeit Datenmenge - Latenz</CAPTION>
<TR><TD>
[width=]./img/v4/plot.jpg
</TD></TR>
</TABLE>
<DIV ALIGN="CENTER">
</DIV>
<HR>
</DIV>
<P>
Abbildung <A HREF="#img:dataLat">25</A> zeigt, dass bei wachsender Datenmenge die Latenzzeiten von immediate und worst case immer weiter auseinanderlaufen. Da in der Praxis die Informationen, welche in Echtzeit benötigt werden, in der Regel kleiner 1 kiloByte sind, empfiehlt es sich die größeren Datenmengen von den Echtzeitinformationen zu entkoppeln und getrennt, niedriger priorisiert, zu übertragen.
<P>
<BR><HR>
<ADDRESS>
Manuel Traut
2007-02-25
</ADDRESS>
</BODY>
</HTML>
|
