EventGhost

Thankjuverumusj! (Think Elvis, or the French agent played by Jean Reno in the previous "Godzilla"! )

It could take the reports one minute after startup without whining, so that's a good sign. It's still running 15 minutes after that!

In torture mode now. I like hurting software! I run new reports every five minutes. Four reports out, still running nicely. The only "database locked" message was witin a minute after EG startup. This may be a winner!

This is no fun! I have to tighten the thumb screw or increase the stretch in the rack (since the iron maiden most likely was a bluff). Down to reports and FTP uploads every 3 minutes for the next hour!

Talk about uppkäftig jävel! It just keeps on ticking! Well, time to go one up: 30 days report every 3 minutes instead of 14 days. I see a good increase in CPU when they are being made (up to around 50 %), but it falls to a normal level again when they're done. But it's rather hopeless to do anything else in EG while they are being made. Which I guess isn't all that unexpected. if I double click an action while this is going on, it pops up when the reports are made. Also most of the stuff that has been ticking in under the report creation comes in a bunch after it's done. But not all. Still I guess that's to be expected, isn't it?

Btw (when I'm spanning the thread) the 30 day graph is pretty revealing. You can see the ten days when nobody were at the cabin, end you can see the three times we washed clothes on the green line. It's a combined "yttergang" and washing room, with a washer and a dryer. The dryer is of the heat pump type and runs a lot cooler than older types, but still it gives a certain effect in a 4 square meter room!

Edit: The hot water tank is in that room as well, that explains why it's never as cool as the rest of the cabin when I'm only running frost guard temps.

Edit 2: I think I see a pattern here: When the reports are being generated events will tick in and actions will be done until a tempdatacapture happens. When that comes in, EG will stop processing events until the reports are done. Is that about right?

Oops... I think I have found a bug. Or omething. Look at this graph. I had been running 30 day graphs for a while, and saw that I didn't see my attic sensor (which has been capturing for a few days). So I deactivated the automatic creation for a while and tried to see the first two days, and then seven days. Both times it kept the 30 days of earlier, but only showed sensor readings for the last two or seven days. None of them showed my attic sensor, even though I took a printout of the database, and it has data. Any idea what's going on here? Creating a brand new combo report action doesn't change anything.

But restarting EG makes it go back to a day or two, if I haven't done a longer report on the same run of EG. If I then do 30 days and go back to 2 I have the same thing.

This seems to be something new, I don't have that problem at home, where I'm running a version from before the threading tests started.

This seems to be something new

Yes, I think so too, I will look at it tomorrow, can't be hard to find (I hope)

I am however happy to hear about the stability it seems to have

Yeah, I think the stability is good! It as now been running all night, with those 30 days reports every ten minutes, and no problems.

Btw it would be nice with an event when a report is done running. I discovered that the website was always one report behind because the FTP upload started only a few seconds after the report generation was started. I have added a delayed event action in the macro, firing the FTP upload, but it's kind of difficult to assess how long time it takes, especially with many reports (at home I plan to have one daily report for each room every hour and bigger reports some time during the night).

Edit 2: I think I see a pattern here: When the reports are being generated events will tick in and actions will be done until a tempdatacapture happens. When that comes in, EG will stop processing events until the reports are done. Is that about right?

Well it is necessary to lock the databases while the report is created, no temp data is lost since we are waiting for the databases to be released and then the pending data will be written (I am releasing the lock as soon as the necessary report data has been fetched). However I have been thinking about and experimenting how the data saving routine threads can be made more independent from main EG, I would also like that EG keeps running without interruption (target is that the icon stays green, when yellow or red it is blocked or busy)

This seems to be something new

I have done some debugging on this topic but this morning everything is just working as expected so I have not found anything wrong yet. The 'Selected period' is showing the available dates of the data. So if you select 30 days it will show the date & time of the first and last data point found in that span

Btw it would be nice with an event when a report is done running

That will be added, that's easy

Krambriw, when I change from 30 to 14 days, the period in the text doesn't change. The dates are the same, but the lines are flat from day 15 and out. So there's something very funky going on there.

Thanks for adding the event, that will be a great help!

OK, I have uploaded a new version that is not locking EG anymore when data points are saved. Now it is not locking anything at all

Event when report is done:

Krambriw, when I change from 30 to 14 days, the period in the text doesn't change. The dates are the same, but the lines are flat from day 15 and out. So there's something very funky going on there.

You are absolutely correct, this is a bug, I can now reproduce it as well, thank you, I will try to hunt this down