I have the same issue, which I suspect is from several SVG graphic in my Image Management folder at a size of 56MB. I have them linked to a container through the CSS under backgroundImage url("/system/images/path/to/image.svg"), then set backgroundSize to "cover" so that it fills the entire container. Why would this hog up short term memory of 2GB? What is short term memory with respects to Ignition, the Gateway and the Perspective WebUI?
This size seems phenomenally high? What do you have in these SVGs?
If you have raster images within them, they should be removed.
I am using Microsoft Visio to overlay some jpg/png onto another jpg/png to update a wide view of one of our facilities. I then save/change file type to SVG of the entire view. This generates near 56MB.
That makes a bitmap inside your SVG. That makes the file size and memory blow up. Don't use jpegs (or any other pixel-based image format) at all.
Xmas list item, get an arial drone to snap a picture of what I need, save this as an SVG. I have been good this year, but not to the extent of getting someone to fly a drone yet. Any suggestions as to what would be my options to overlay snip-its from images of buildings that were built later to the over all view, to then save as SVG at a smaller file size?
And how do you expect to save a photograph as a non-pixel-based image format inside an SVG?
You need a pure vector graphic, not any kind of photo or photo format.
You should ask your mechanical/civil engineering group to export your facility plan view drawing as an SVG and prune that down.
Don't. Draw vectors instead of embedding photos.
To expand on this a little bit: SVG isn't a compression format. It's a fundamentally different model of how an image works - there's raster formats like BMP, PNG, JPEG - or there's vector formats like SVG. The whole thing with SVG is that it's literally an XML file containing a bunch of line/circle/shape/point definitions in a coordinate space. It also contains the ability to "embed" raster images - but then you're getting none of the benefits of SVGs (arbitrary scaling to other resolutions) and none of the benefits of your chosen raster format's compression (because SVG is plain text, so your data will always be written out in some chunky text format like b64 anyways).
If you have raster images you want to use as backgrounds for views, just save those raster images in some format that's good for compression like JPEG (if you can accept minor loss in quality, which is usually acceptable for photos). Filesizes should be drastically smaller and therefore less of a hit on the IDB. If it's still not enough, stand up a true file server like nginx or Traefik or something else on the same host as the gateway and use that to serve up your static images - it'll avoid the load on the gateway and probably be faster, to boot.
If you get a nice Xmas bonus, get Faro Technologies in to scan your building (roof), they export as SVG
Can't afford the drone or scanner? Just google it; https://mapsvg.com/docs/basics/download-svg-with-google-map
1 Like