# Node-red-contrib-inspector fail with 32 bits os?
**URL:** https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461
**Category:** General
**Tags:** function-node
**Created:** [1 October 2022 16:51 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461 "2022-10-01T16:51:56Z")
**Posts on this page:** 8
**Page:** 5
### Author:  [@henkkas](https://discourse.nodered.org/u/henkkas)
#### Post date: [8 October 2022 14:45 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/81 "2022-10-08T14:45:38Z")
> [@Colin](#):
>
> What do you mean by 'compile'?
Sorry, deploy.
---
### Author:  [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [8 October 2022 14:51 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/82 "2022-10-08T14:51:38Z")
> [@henkkas](#):
>
> I have a lot of settings in global data.
> Is it possible to backup the data to a file in order to restore later on new system?
Do you mean global context?
You can set NR to use persistent storage, which will save all the data in a file.
Presumably you can transfer that file to the other Pi.
Or you can use the opportunity to rewrite with fewer global variables 🙃
---
### Author:  [@henkkas](https://discourse.nodered.org/u/henkkas)
#### Post date: [8 October 2022 14:59 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/83 "2022-10-08T14:59:27Z")
I did that intentionally, so that's no option for me. 😉
---
### Author:  [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [8 October 2022 15:05 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/84 "2022-10-08T15:05:37Z")
I think it is most unlikely that you have a corrupted deploy (unless you have a dodgy SD card). Did you keep a backup of a flow showing a problem so we can analyse it properly.
---
### Author:  [@henkkas](https://discourse.nodered.org/u/henkkas)
#### Post date: [9 October 2022 09:24 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/85 "2022-10-09T09:24:58Z")
@Colin At the moment I am focusing on rebuilding my project on second rpi.
---
### Author:  [@henkkas](https://discourse.nodered.org/u/henkkas)
#### Post date: [23 October 2022 13:07 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/86 "2022-10-23T13:07:39Z")
@Colin @dceejay @jbudd @BartButenaers @TotallyInformation ,
After quit some work, I managed to configure the second RPI 3B+, that I have, so I can experiment with it to try solving my problem, without disturbing my running project. After restoring flows and databases, I found I still have the problem with increasing CPU usage overtime. I tried lots of stuff, like switching of many parts of the application, delete databases, etc..., but nothing seems to help (Of course every time I had to wait quit a while to see the result.
While I was seeing no solution there I started to examine the whole application and finally after quit some work I found I very tricky loop. So I am very glad, I found the course of the problem!!!
The whole experience was a very good learning curve for me in many ways.
Some points here:
As I installed the latest 64-bit OS Debian 11 on RPI 3B+, I found that my application then uses about 65% of memory, in comparison, my current project 32-bits OS uses only about 40% of memory. I didn't see much better performance on the 64-bit OS though! So for me, I decided not to go for 64-bit OS in the near future for my application yet. Maybe when I would opt for a RPI 4B, I will consider it.
I also tried using bart's `node-red-contrib-v8-cpu-profiler` that also was an eye opener, but it didn't really help with my problem in this case. Maybe some problems in the future.
Influx. Among the influx nodes there is a backup node. Very easy to use, but there is no "Restore"-node. So I didn't know how to restore the databases in an easy way. Now that I have been playing around with the commands:
> $ influxd backup -portable \ \
> $ influxd restore -portable \ \
_Note: \ is optional. If left out, all databases will be backed-up or restored._
Because I found it was very easy, I am constructing a standard routine for this option.
Those were some of my experiences, hope they were helpful for some in a way.
Anyway, I want to thank you for all your help given to me so far.
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [23 October 2022 19:28 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/87 "2022-10-23T19:28:35Z")
> [@henkkas](#):
>
> As I installed the latest 64-bit OS Debian 11 on RPI 3B+, I found that my application then uses about 65% of memory, in comparison, my current project 32-bits OS uses only about 40% of memory. I didn't see much better performance on the 64-bit OS though!
Yes, that would be expected. Since memory addresses can be twice as long. If I remember rightly, you don't see any real benefit until you have 4GB+ or RAM.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [6 November 2022 19:29 UTC](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461/88 "2022-11-06T19:29:20Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.nodered.org/t/node-red-contrib-inspector-fail-with-32-bits-os/68461.md?page=4)