01.12.2012 Views

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Effect <strong>of</strong> the Degree <strong>of</strong> Neighborhood on Resource Discovery 183<br />

Matchmak<strong>in</strong>g efficiency, response time and the message complexity are analyzed<br />

<strong>in</strong> these experiments. Message complexity analysis is expla<strong>in</strong>ed <strong>in</strong> Section<br />

5. The matchmak<strong>in</strong>g efficiency <strong>in</strong> time <strong>in</strong>terval T =[Tstart,Tend] is def<strong>in</strong>ed as:<br />

(<br />

Tend �<br />

Tstart<br />

Tend �<br />

Matched Message/<br />

Tstart<br />

T otal Message)∗100<br />

Where Tstart and Tend represent the start and end time <strong>of</strong> the time <strong>in</strong>terval<br />

T =[Tstart, Tend]. The response time denotes the time <strong>in</strong>terval, start<strong>in</strong>g from<br />

the time a message is received, and ends at the moment when a match is found for<br />

the received message. The response time is calculated as: RT = Tmatch−Treceive,<br />

where RT represents the response time, Tmatch is the time when the matchmaker<br />

agent found a match<strong>in</strong>g <strong>of</strong>fer/request for the received request/<strong>of</strong>fer message and<br />

Treceive is the receiv<strong>in</strong>g time <strong>of</strong> the received request/<strong>of</strong>fer message.<br />

All the experiments are executed <strong>in</strong> different network conditions, <strong>in</strong>clud<strong>in</strong>g<br />

task <strong>in</strong>tensive (tasks >> resources), balanced (tasks ≈ resources) andresource<br />

<strong>in</strong>tensive (tasks 1 <strong>in</strong> Figure 4a). The completely centralized approach shows higher<br />

matchmak<strong>in</strong>g efficiency for small workloads. However, one matchmaker cannot<br />

ma<strong>in</strong>ta<strong>in</strong> its matchmak<strong>in</strong>g efficiency with the <strong>in</strong>creas<strong>in</strong>g work load. The matchmak<strong>in</strong>g<br />

efficiency keeps on decreas<strong>in</strong>g with <strong>in</strong>creas<strong>in</strong>g work load <strong>of</strong> the matchmaker.<br />

This phenomenon can be understood with the follow<strong>in</strong>g explanation.<br />

With the <strong>in</strong>creas<strong>in</strong>g workload, the matchmaker has to process more messages,<br />

so it takes more time to f<strong>in</strong>d matched pairs. This results <strong>in</strong> an <strong>in</strong>creased response<br />

time <strong>of</strong> the matchmaker. S<strong>in</strong>ce each request/<strong>of</strong>fer message has a validity<br />

period (TTL), therefore the TTL <strong>of</strong> the request/<strong>of</strong>fer messages start expir<strong>in</strong>g<br />

with <strong>in</strong>creased process<strong>in</strong>g time <strong>of</strong> the matchmaker and consequently the matchmak<strong>in</strong>g<br />

efficiency <strong>of</strong> the matchmaker decreases with <strong>in</strong>creas<strong>in</strong>g workload <strong>of</strong> the<br />

matchmaker. The work load threshold for one matchmaker system, decreas<strong>in</strong>g<br />

matchmak<strong>in</strong>g efficiency with <strong>in</strong>creas<strong>in</strong>g workload <strong>of</strong> a matchmaker are expla<strong>in</strong>ed<br />

<strong>in</strong> our earlier work [13].<br />

The matchmak<strong>in</strong>g efficiency <strong>of</strong> multiple adaptive matchmakers approach<br />

is not affected by the <strong>in</strong>creas<strong>in</strong>g workload. The adaptive mechanism <strong>in</strong>troduces

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!