Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[aussie mate]

Just wondering if anyone else has noticed that Bluewatch seems to be utilising most of the CPU & memory.

General it seems to be between 50-90% of CPU & 84,000-135,000k of memory

Is this normal?

It is slowing down my PC...

[Tuicemen]

There was some talk about the CF4.dlls which BlueWatch uses having a memory leak issue. I had assumed this issue was addressed and fixed as I initially didn't see it.
It seems to be more noticeable if you have multiple Bt Devices or devices which don't send a constant detection.
I now see the memory used continually rises (when detection info is gathered) but I don't see a CPU issue it may spike 5% -10% with detection but drops back down to the constant.
aussie mate
For now schedule a BlueWatch restart for a time that is convenient.(there is an option for this both in the time and X10 triggers)
This will free used memory and any CPU resources BlueWatch is using.
As a tip set BlueWatch so it sees devices as connected on start up.

I'll dig into this a little more and see what else I can come up with.
I've been playing with other bluetooth dlls both in C# and VB so I may have to convert to using one of those.
As long as they don't have the same issues.
 

[Tuicemen]

Good News Update:
I've found a dll that in tests is looking real promising, it uses 1/3 the memory verses the CF4 .dlls
It also has a ping option that in my tests actually works! 
Since C# is notoriously bad at getting rid of garbage and I have to recode the whole project anyways I'm going to convert BlueWatch to VB code.
Hopefully this won't be a long drawn out process.
I have most of the BT detection coded and just need to add in the options that are already in BlueWatch.
I've kept the layout very similar so users won't have to relearn it.
I'll keep you updated with the process and hopefully have a beta version ready soon.

If any BlueWatch users wish to beta test the new version, drop me an email and I'll add you to a beta tester list.
It may get features your looking for added sooner
 

[Tuicemen]

UpDate:
This isn't going as quickly as I had originaly thought it would!  
Some code just doesn't convert well 
I had originaly thought I could do away with the dual loss detect but it looks Like it is still needed. at least here anyways.
I'm about half way done with adding the current options. So possibly by the end of the week I'll have a beta test out for those BlueWatch users wishing to give it a go.
The cool thing about the VB code is it handles the garbage better then the C# code.
The Vb version is slightly larger in size but it uses way less memory even on initial start up.