question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New option for Homebridge_OPTS

See original GitHub issue

Hello everybody, i have 24 Homebridge instances running as systemd service, one instance for each plugin.

What has always disturbed me and synonymous has reduced the system speed is that every instance starts all the plugins from global installed / usr / lib / node_modules. By a note from another user, the solution became aware of the -P option to use. To test I have installed all the plugins local what a little more cumbersome the conventional way and started with the -P option.

Now each instance just launches the plugin it needs. If I install the plugins globally in / usr / lib / node_modules I have a random access memory consumption when all 24 instances are started from 2.5GB. With an installation of the plugins locally is that only each instance the plugin loads what it needs at 700 MB. Here is a huge performance difference especially for raspberry pi user.

My own hardware is an Intel nuc, because with the raspberry pi 3 the random access memory was no longer sufficient. On my raspberry pi 3 I could start a maximum of 10 instances. I think that many users use their Homebridge with multiple instances because the advantages are very big compared to the single instance.

I have also tried using the -P option to start the instances when the plugins are installed in / usr / lib / node_modules. Unfortunately all plugins will be loaded in every instance. I also received this message:

skipping plugin found at '/ usr / lib / node_modules / homebridge-sun-position' since we already loaded the same plugin from '/ usr / lib / node_modules / homebridge-sun-position'.

Would not it be useful here to create maybe a new option -X for the (config option) in homebridge which still allows the plugins globally to be installed under / usr / lib / node_modules. This would allow for each instance only the plugin to start what is needed without reinstalling all plugins to local.

For the ever larger Homebridge setups of the users I think that it would be a great new feature.

Greeting Nastra

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:4
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
theo-69commented, May 21, 2018

Great Idea

0reactions
Nastrascommented, Jun 6, 2018

#1880 solved!

Read more comments on GitHub >

github_iconTop Results From Across the Web

homebridge-unifi-protect/FeatureOptions.md at main - GitHub
homebridge -unifi-protect will log all devices it discovers on startup, including MAC addresses, which you can use to tailor the feature options you'd...
Read more >
Homebridge guide: How to make everything HomeKit ...
From the web interface, you can manage your Homebridge plugins, which give you control over devices that don't normally have Homebridge support.
Read more >
New to homebridge and was curious about my options - Reddit
Hey all! So I just recently discovered homebridge and wanted to pretty much just list off everything I've got and see what y'all...
Read more >
Homebridge
Homebridge adds HomeKit support to your non-HomeKit smart home devices.
Read more >
oznu/homebridge - Docker Image
version: '2' services: homebridge: image: oznu/homebridge:latest restart: always ... volumes/homebridge:/homebridge logging: driver: json-file options: ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found