So how to diagnose slow downs:
-
odds are these are running out of memory. In another thread there is a discussion on how to see the hub's memory status (if running current version of FW)
[Wiki] Hidden Features -
so what can you do about it?
- assuming you are running current firmware (that has the most fixes for any memory leaks):
- you can try trimming your db further
Fastest my hub has ever been
[Wiki] Hidden Features
- you can try trimming your db further
- you can try to reduce apps and their use of memory
- this might be reduce how frequently they run (and therefore how much they try to store in state / settings variables
- weather apps have been notorious memory, events, and DB hogs
- this might be uninstalling apps things, (which I know may be painful)
- assuming you are running current firmware (that has the most fixes for any memory leaks):
In general
- the Hub has a fixed amount of memory (today's total is 1GB for OS, JVMs, etc)
- I'm sure HE will offer us a hub with more memory one day
- anyone can run it out by just keep installing more and more things
- the database can be a big consumer of resources, so reducing the number of events it stores reduces the amount of memory it needs - this has been my first go-to to get more available memory.
- app writers can try to be more memory and db friendly, but this another whole discussion on tricks for this
- you can see 'some' of the memory an app uses by looking at settings, state, events for an app or driver. This is in the 'gear' icon next to the app or device (HE console -> apps, HE console -> devices)