8.5 Evaluation and Summary
8.5.1 Query Results
The issued queries yielded the following results:
Query I: Frankfurt to India
<con>
<name>Bangalore</name>
<name>India</name>
</con>
<con>
<name>Madras</name>
<name>India</name>
</con>
<con>
<name>Hyderabad</name>
<name>India</name>
</con>
<con>
<name>Calcutta</name>
<name>India</name>
</con>
<con>
<name>Mumbai</name>
<name>India</name>
</con>
3Some visual differences, however, may be traced back to eXist’s serialization functionality.
In the virtual model, there exist no XLink elements. Albeit if a query result never contains XLink elements, a non-XLink element may have XLink children, e.g. theairportlink inside eachconnectionelement. Due to the straightforward XML serialization of eXist, these children are output straight from their physical representation, instead of being filtered out by the serializer. Nevertheless, thequerying itself performs correct, since the direct query results are XLink-free. Outputting the result nodesincluding their child and attribute nodes is more a custom than a convention, and does not touch the validity of the query answer.
8.5. EVALUATION AND SUMMARY 133
Query I (Germany to India)
0 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300
1259.691s 10.409s
run 1 1193.058s 9.890s
run 2 1340.855s 10.641s
run 3 1323.708s 9.753s
run 4 1276.436s 10.047s
run 5 1201.478s 9.8665s
run 6
1265.871s 10.101s
computed average
seconds
Figure 8.3: Runtime of Query I in the virtual LinXIS model (white) and in the physical model using Saxon (gray)
In words: the query returned five flight connections from Frankfurt to India:
1. Frankfurt→Bangalore 2. Frankfurt→Madras
3. Frankfurt→Hyderabad (India) 4. Frankfurt→Calcutta
5. Frankfurt→Mumbai
8.5.2 Query II: All Connections from Hannover to Lisbon
Figure 8.4: Runtime of Query II in the virtual LinXIS model (white) and in the physical model using Saxon (gray)
<con>
<connection xlink:type="arc" dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes"
xlink:from="iata-HAJ" xlink:to="iata-FRA" distance="174">
<flight dep="05.40" arr="06.40" no="LH1001" .../>
<flight dep="06.15" arr="07.15" no="LH1001" .../>
<flight dep="07.00" arr="08.00" no="LH1003" .../>
<flight dep="07.15" arr="08.15" no="LH1003" .../>
<flight dep="09.55" arr="10.55" no="LH1005" ...>
<above>Exc. 5/17 - 5/20, 5/27 - 5/28</above>
</flight>
<flight dep="11.30" arr="12.30" no="LH1007" .../>
<flight dep="13.20" arr="14.20" no="LH1009" .../>
<flight dep="13.40" arr="14.40" no="LH1009" ...>
<above>Eff. 5/2, Exc. 5/18, 5/27 - 5/28</above>
</flight>
<flight dep="14.30" arr="15.30" no="LH1011" .../>
<flight dep="18.50" arr="19.50" no="LH1013" .../>
</connection>
<connection xlink:type="arc" dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes"
xlink:from="iata-FRA" xlink:to="iata-LIS" distance="1165">
<flight dep="06.45" arr="08.40" no="LH2174" .../>
<flight dep="09.30" arr="11.25" no="LH4530" .../>
<flight dep="13.30" arr="15.25" no="LH2172" .../>
<flight dep="13.40" arr="15.35" no="LH4532" .../>
<flight dep="19.15" arr="21.10" no="LH2176" .../>
<flight dep="21.55" arr="23.50" no="LH4536" .../>
</connection>
</con>
8.5. EVALUATION AND SUMMARY 135
<con>
<connection xlink:type="arc" dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes"
xlink:from="iata-HAJ" xlink:to="iata-MUC" distance="298">
<flight dep="07.05" arr="08.15" no="LH1017" .../>
<flight dep="08.50" arr="10.00" no="LH1021" .../>
<flight dep="11.10" arr="12.20" no="LH1025" ...>
<above>Exc. 5/27 - 5/28</above>
</flight>
<flight dep="13.05" arr="14.15" no="LH1027" .../>
<flight dep="15.10" arr="16.20" no="LH1019" ...>
<above>Exc. 5/27, 6/8</above>
</flight>
<flight dep="17.15" arr="18.25" no="LH1029" .../>
<flight dep="19.00" arr="20.10" no="LH1033" .../>
<flight dep="20.35" arr="21.45" no="LH1035" ...>
<above>Exc. 5/17 - 5/18, 6/7 - 6/8</above>
</flight>
</connection>
<connection xlink:type="arc" dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes"
xlink:from="iata-MUC" xlink:to="iata-LIS" distance="1234">
<flight dep="06.35" arr="08.40" no="LH2212" .../>
<flight dep="11.10" arr="13.20" no="LH4540" .../>
<flight dep="14.10" arr="16.15" no="LH2170" .../>
<flight dep="19.05" arr="21.15" no="LH4544" .../>
</connection>
</con>
</result>
In words: The database contains two connections from Hannover to Lisbon: one going via Frankfurt am Main, the other one via Munich.
8.5.3 Query III: All Connections from Munich, Germany to Auckland, New Zealand without Stopover in the U.S.
<connection xlink:type="arc" xlink:from="iata-MUC" xlink:to="iata-HKG" distance="5610"
dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes">
<flight dep="21.40" arr="15.10+1" no="LH730" type="343" stops="0" meals="MM"/>
</connection>
<connection xlink:type="arc" xlink:from="iata-HKG" xlink:to="iata-AKL" distance="5704"
dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes">
<flight dep="18.10" arr="09.00+1" no="LH9810" op_by_partner="yes" type="744" stops="0"
meals="DB"/>
</connection>
</con>
<con distance="11416">
<connection xlink:type="arc" xlink:from="iata-MUC" xlink:to="iata-BKK" distance="5455"
dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes">
<flight dep="21.10" arr="12.40+1" no="LH9716" op_by_partner="yes" freq="346" stops="0"
meals="M"/>
</connection>
Query III
(Munich to Auckland without U.S.)
0
Figure 8.5: Runtime of Query I in the virtual LinXIS model (white) and in physical model using Saxon (gray)
<connection xlink:type="arc" xlink:from="iata-BKK" xlink:to="iata-AKL" distance="5961"
dbxlink:transparent="group-arc-elem drop-to-elem ins-to-nodes">
<flight dep="19.40" arr="11.40+1" no="LH9738" op_by_partner="yes" freq="346"
stops="0" meals="M"/>
</connection>
</con>
</allcons>
</result>
In words: The database contains two connections from Munich to Auckland:
one via Hong Kong (11314 miles) and one via Bangkok (11416 miles). Two more results exist over San Francisco and Los Angeles, but they are filtered from the result since the cities are in the United States.