× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 14-Dec-2015 13:02 -0600, Mark Murphy/STAR BASE Consulting Inc. wrote:
<<SNIP>> Years ago I made a broker using a data queues to send data
to multiple systems. It was extremely fast, but if the data queue got
more than say 100 messages deep, it was 10 times slower. I think you
can regulate that by setting the initial size of the data queue, but
I never did any testing to verify my hypothesis.

If "years" goes back to pre-v3r1 or perhaps early v3r1, then since then, the horribly slowed queue issue was addressed and rectified. The /old/ implementation was *horrible*, whereby all of the enqueued data was getting _moved_ elsewhere whenever a new message was added and\or a message was removed\dequeued [I do not recall the specifics], then all of that moved data was getting _moved back_ /onto/ the queue.

I knew about the issue and the resolution, because the DBXREF is implemented using the same underlying LIC methods as user queues. The negative impact was so noticeable, that either the LIC queue feature needed to /correct/ the design to allow the [since changed from a single-queue to a dual-queue feature] to operate with sufficient throughput, or the DBXREF would have had to implement an alternative queue [and that probably would have been using a list of spaces, implemented entirely above the LIC except for ensuring atomicity].


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.