vis adapter instantiation is hanging

[HarryHpd]

I am not able to install iobroker.vis

it appears to me, the problem is not in vis but in iobroker.web instantiation.

The process is hanging at

the same problem appears if I try to create a iobroker.web instance.

Systeminfos

Plattform: linux
Betriebssystem: linux
Architektur: x64
CPUs: 2
Geschwindigkeit: 2901 MHz
Modell: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz
RAM: 0 MB
System-Betriebszeit: 01:56:48
Node.js: v18.18.2
time: 1700073089052
timeOffset: --
NPM: 9.8.1
Adapter-Anzahl: 510
Datenträgergröße: 7.8 GB
Freier Festplattenspeicher: 3.0 GB
Aktive Instanzen: 10
Pfad: /opt/iobroker/
Betriebszeit: 01:26:24
aktiv: 

[Apollon77]

Did you checked your computer? Is anything on 100% CPU? Mem issue? any indication of othert issues?

[HarryHpd]

... Oh dear, you are on the right track.

my sandbox iobroker sits on a proxmox server and I had indeed very limited memory (1Gb). After increasing it to 4Gb instantiation is done within seconds.

You can close this issue.

Many thanks

Am Do., 16. Nov. 2023 um 09:48 Uhr schrieb Ingo Fischer < @.***>:

Did you checked your computer? Is anything on 100% CPU? Mem issue? any indication of othert issues?

— Reply to this email directly, view it on GitHub https://github.com/ioBroker/ioBroker.vis/issues/801#issuecomment-1814019220, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQ5PGCAHCWZ27EA6YMCALDYEXHOPAVCNFSM6AAAAAA7NYVP3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGAYTSMRSGA . You are receiving this because you authored the thread.Message ID: @.***>

[HarryHpd]

Add on....

4Gb of memory was still not enough to instantiate echart es well.

After increasing it to 8Gb I got it to finalize this instantiation.

Am Do., 16. Nov. 2023 um 09:48 Uhr schrieb Ingo Fischer < @.***>:

Did you checked your computer? Is anything on 100% CPU? Mem issue? any indication of othert issues?

— Reply to this email directly, view it on GitHub https://github.com/ioBroker/ioBroker.vis/issues/801#issuecomment-1814019220, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQ5PGCAHCWZ27EA6YMCALDYEXHOPAVCNFSM6AAAAAA7NYVP3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGAYTSMRSGA . You are receiving this because you authored the thread.Message ID: @.***>

[MichaelSchaaf999]

echarts seems to be a memory-eater - here as well. And the usage slows down the system performance: Can be demonstrated if this adapter is de-activated (Proxmox performance graphics)

[HarryHpd]

... good to know. I am currently in a evaluation phase and a iobroker newbie. I am not sure which graphics engine I will use for my time series. I know grafana for a long time. I just tried e-charts now, because I thought it might be the only choice I have to integrate time series charts in vis.

Am Do., 16. Nov. 2023 um 11:50 Uhr schrieb MichaelSchaaf999 < @.***>:

echarts seems to be a memory-eater - here as well. And the usage slows down the system performance: Can be demonstrated if this adapter is de-activated (Proxmox performance graphics)

— Reply to this email directly, view it on GitHub https://github.com/ioBroker/ioBroker.vis/issues/801#issuecomment-1814205820, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQ5PGEVKLJNCUZS5JUWO4TYEXVWBAVCNFSM6AAAAAA7NYVP3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJUGIYDKOBSGA . You are receiving this because you authored the thread.Message ID: @.***>

[Apollon77]

Ok thats all interesting ... and yes intertingly enought echarts (and also web?) seems siometimes have issues when beuing uploaded. (@foxriver76 another case). Please share yiur nodejs versions and such.

When echarts needs too much CPU when running please open an echarts issue with details

[Feuer-sturm]

@Apollon77 I see the issue of massive RAM consumption on different adater updates (uploads) like vis2, fullcalender as well. Currentl my production system has 8 GByte RAM which are sporadically necessary to update some adapters. This problem should be tracked somewhere else (js-controller??) but I think it is not a vis specific issue.

[foxriver76]

Is it during the npm install or during upload?

[Feuer-sturm]

@foxriver76 on my system during upload

[foxriver76]

Then controller issue

[Feuer-sturm]

@foxriver76 Issue created https://github.com/ioBroker/ioBroker.js-controller/issues/2538