D
David
Hi all,
In my earlier post about Application design, I was informed about the MSMQ.
Having never used MSMQ before, I have now done quite a bit of research. In
some respects, it seems almost perfect for what I need, but in others, I am
not so sure.
For example, for the reading of messages, most of the examples show just a
few seconds before retrieving messages with a timespan in the order of 2 or
3 seconds. Is this normal? The reason I ask is that the system I need to
develop can get VERY HEAVILY loaded at times and I think two or three
seconds is probably way too much time to waste. However, what I don't want
to do is to overload the system with checking for messages when there are
none.
What would be a good compromise. I need a queueing system but I also need
near instant response when I can. (Near instant for example is to have
returned a response whilst still processing a thread, so in the order of
milliseconds)
Something else the examples fail to do is to show which machine the messages
should be stored on. I am assuming local and that other machines that need
to act on the messages call the message from the local machine. Am I
assuming correctly?
The main use of the system I have to develop is an image interpretation
engine. Basically, the engine can interpret about 3000 parts of an image per
second. Sometimes there will be little for it to do, sometimes there could
be many thousand parts coming in all at once.
To scale this scenario, I would expect that we would just add processing
servers with the image interpreting engine installed.
The end application (that I am building) requires where possible that there
is a near instant response. We will be putting in logic to try and help with
the workload... we need an instant queue which will work on certain parts of
the image to validate the mandatory requirements, and a near-instant queue
that will handle the parts of the image that doesn't require the immediate
work.
Is MSMQ what I need? If not, then what else could I use?
(I don't want to get bogged down with threads, though I think threads will
have a major role to play in this application. (When I say Bogged Down, I
mean that the machine is likely to suffer when there is a LOT of traffic
coming in.))
--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available
In my earlier post about Application design, I was informed about the MSMQ.
Having never used MSMQ before, I have now done quite a bit of research. In
some respects, it seems almost perfect for what I need, but in others, I am
not so sure.
For example, for the reading of messages, most of the examples show just a
few seconds before retrieving messages with a timespan in the order of 2 or
3 seconds. Is this normal? The reason I ask is that the system I need to
develop can get VERY HEAVILY loaded at times and I think two or three
seconds is probably way too much time to waste. However, what I don't want
to do is to overload the system with checking for messages when there are
none.
What would be a good compromise. I need a queueing system but I also need
near instant response when I can. (Near instant for example is to have
returned a response whilst still processing a thread, so in the order of
milliseconds)
Something else the examples fail to do is to show which machine the messages
should be stored on. I am assuming local and that other machines that need
to act on the messages call the message from the local machine. Am I
assuming correctly?
The main use of the system I have to develop is an image interpretation
engine. Basically, the engine can interpret about 3000 parts of an image per
second. Sometimes there will be little for it to do, sometimes there could
be many thousand parts coming in all at once.
To scale this scenario, I would expect that we would just add processing
servers with the image interpreting engine installed.
The end application (that I am building) requires where possible that there
is a near instant response. We will be putting in logic to try and help with
the workload... we need an instant queue which will work on certain parts of
the image to validate the mandatory requirements, and a near-instant queue
that will handle the parts of the image that doesn't require the immediate
work.
Is MSMQ what I need? If not, then what else could I use?
(I don't want to get bogged down with threads, though I think threads will
have a major role to play in this application. (When I say Bogged Down, I
mean that the machine is likely to suffer when there is a LOT of traffic
coming in.))
--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available