Hypfer / ICantBelieveItsNotValetudo

A Valetudo companion service which renders maps to pngs
Apache License 2.0
129 stars 80 forks source link

High cpu usage on valetudo 0.6.1 #32

Closed ghost closed 3 years ago

ghost commented 4 years ago

Every since upgrading to valetudo 0.6.1, the mapper consumes about a full core on a i7-7700T The config beeing

{
  "mapsettings": {
    "drawCharger": true,
    "drawPath": true,
    "drawRobot": true,
    "scale": 4
  },
  "mqtt": {
    "autoconfPrefix": "homeassistant",
    "broker_url": "mqtt://mosquitto.homeassistant",
    "identifier": "Roborock",
    "mapDataTopic": "valetudo/Roborock/map_data",
    "minMillisecondsBetweenMapUpdates": 5000,
    "publishMapImage": true,
    "topicPrefix": "valetudo"
  },
  "webserver": {
    "enabled": false,
    "port": 3000
  }
}

And the usage looks like this

Screenshot 2020-08-04 at 12 49 46
Hypfer commented 4 years ago

Yep.

The current implementation performs abysmal and only exists at all because I wanted to avoid "but but but RE does thing" nagging. I don't have any use for this service

kubiq commented 4 years ago

You can make the map smaller with scale 2 or so, that will help for now

Hypfer commented 3 years ago

Thanks to @mikispag this is now solved