Re: Data queue space

["James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>]

Mark,

So I could think of a data queue as a PF with reuse delete *yes, and if
it's a FIFO or LIFO queue is has a hidden timestamp index to keep things
in order?

If that's the case, it does make it a more workable solution.  I just
imagined thousands of zip code lookups per day, day after day just
consuming space.

One last concern though, and with the current speed of machines it may
be moot, but what is the performance curve on a data queue?  I
understand they get slower the bigger they get.

I've used the data queue method for piping on demand print functions and
that does work really slick.  We have bar code readers that scan a
product as it comes through a particular station and that triggers a
Zebra printer to spit out a shipping label and customer specific
inventory label(s), so I'm not against the idea of data queues, just
wondering if they are the best method for record level get operations.

Just to change the subject a little, has anyone tried using message
queues instead of data queues?  I've never used the product, but isn't
the MQ product line based upon data exchange through Message Queues?



"M. Lazarus" wrote:

> 
>   Data queues don't automatically get smaller, but as I understand it, the
> removed entry can get replaced w/ a new entry.  It's only when you have
> sharp spikes in size that you might have a problem.
> 
>   -mark
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---