@Poxford wrote:
Whenever I'm trying to save my data, I'm getting the original error of everything getting back logged. My producer loop is very fast and I believe a small part of the time, but I guess I'm confused how the queue knows when to tell the producer loop to send another set of data without the producer just constantly running.
The Queue doesn't know anything, it is just a "dumb conduit". Again, I haven't seen your code, but you should have created a Queue without specifying a size, which allows it to "grow as needed". Hmm, I don't recall (and it is easier and safer to just ask you here) how fast your Producer Loop runs and how much data it puts on the Queue each time it loops -- clearly if you are trying to put 1MByte of data every millisecond, you're going to have a problem ...
How fast does your Producer Loop run? How big is the Array of Dbl that you are putting on the Queue? Is your Queue of an unbounded size?
The reason for asking these questions is that a Queue can "expand" -- you can have multiple entries on the Queue. In some circumstances, you'll get better performance (because you won't need to constantly allocate memory) if you know, in advance, that (say) no more than 20 items will need to be enqueued, so you Obtain a Queue of fixed length, 20 items, you pre-fill the Queue with 20 items (note if you are using Arrays, fill it with Arrays of the correct size!) to get all the Memory allocated, then Flush the Queue (clearing the memory). Now the Memory is ready for use.
In most instances, one just uses an unbounded Queue, and there's no problem. But you seem to be having a problem. Maybe it's time to post another Zip file with the reworked code, showing the Producer/Consumer design. You do know, I hope, that the Consumer part of the code is in its own While Loop, completely separate (except being "connected" by the Queue coming into both loops) from the Producer, which I recall is embedded in a State Machine ...
Bob Schor
