Why do shorter destination names perform better than long destination names?

Why do shorter destination names perform better than long destination names?

book

Article ID: KB0091862

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Assume the following destination names:

  CLIENTNAME.FOO1.GROUP2.BAR3
            vs
  CLNT.F1.G2.B3

The shorter destination name would result in better performance because:

- It takes less space on the message wire  which means less traffic and less to store.
- The greater the length of each token the greater the time required to compute the destination’s hash value.
- Searches for destinations with many similar tokens are more expensive than those where the tokens differ early on.

Issue/Introduction

Why do shorter destination names perform better than long destination names?