- This topic has 3 replies, 2 voices, and was last updated 2025-04-17 at 3:15 am by
.
-
Posts
-
-
Hi Ray,
My client experienced a few ‘Out of Memory’ Pop-ups from the Dispatcher.
Today I received the *.csl files to have a look at and I did notice something.
The logging files are restricted to 10Mbytes, if larger then I start a new file.
Usually, the last entry in the file has the same timestamp as the file itself, which makes sense.
But now I noticed that gradually the timestamp of the last message is earlier than the timestamp of the file.So I suspect that the Dispatcher is not keeping up with the rate of messages that it receives.
And this increasing backlog of messages probably is eating up the memory?Is there a way that I can detect that this is happening?
So maybe I can tune the amount of messages that I am sending?Kind regards,
Hans -
Hi Hans,
I’m not sure what happened to your message content. I received the message content in the notification message (now that I have them turned back on). I’ve included it below.Are you able to send me some of the log files? If so, please zip them up and send them to support@raize.com.
Also, are you using the MaxSize and MaxParts properties to control the size of the log files? Or, are you doing that yourself?
The Dispatcher does have an internal queue that new messages are put into when they arrive. The load on the Dispatcher is reflected in the tray icon for the Dispatcher, if you have that visible. The interior of the icon shows varying shades of yellow to indicate load. There is no way to programmatically acquire the Dispatcher load.
What types of data are you capturing in CodeSite? Simple data types, or objects, images, etc. I can also get this from the sample log files, if you are able to send them to me.
Ray
>>>>
Hi Ray,My client experienced a few ‘Out of Memory’ Pop-ups from the Dispatcher.
Today I received the *.csl files to have a look at and I did notice something.
The logging files are restricted to 10Mbytes, if larger then I start a new file.
Usually, the last entry in the file has the same timestamp as the file itself, which makes sense.
But now I noticed that gradually the timestamp of the last message is earlier than the timestamp of the file.So I suspect that the Dispatcher is not keeping up with the rate of messages that it receives.
And this increasing backlog of messages probably is eating up the memory?Is there a way that I can detect that this is happening?
So maybe I can tune the amount of messages that I am sending?Kind regards,
Hans
<<<< -
Dear Ray,
Thank you for your attention.
The rotating of the files is done using MaxSize and MaxParts.
TCodeSiteDestination* dest = new TCodeSiteDestination(this);
dest->LogFile->FileName =
“LaserToolLog” + howlate.FormatString(“yyyymmmdd_hhnn”) + “.csl”;
dest->LogFile->FilePath = “$(MyDocs)”;
dest->LogFile->MaxSize = 10000; // Limit to 10 MByte
dest->LogFile->MaxParts = 0; // Do not limit number of parts
dest->LogFile->Active = true;The load on the Dispatcher is reflected in the tray icon for the Dispatcher, if you have that visible.
The client uses my software unattended, so there is no human to monitor the tray icon.The data logged are mostly simple one-sentence messages.
Like Send, SendMsg and SendWarning, etc.
And EnterMethod and ExitMethod messages.If I look in the logging then about 160 messages are sent every second.
This seems to fast for the Dispatcher to keep up to.I will send you a logging file.
Kind regards,
Hans -
160 messages per second is a bit high. For short bursts, that should not cause any issues, but if this rate was over a longer time period, it could certainly put an extra strain on the dispatcher.
You mention that the Out of Memory error is happening on your client’s machine. I’m curious if you have seen this same behavior on your machine? I’m curious as to the memory capacity of the client machine.
Ray
-
- You must be logged in to reply to this topic.