I’m using Panel Pipelines to build a complex app with many pages (parameterized classes). From the Panel docs:
Pipeline stages may be either Parameterized instances or Parameterized classes. With classes, the class will not be instantiated until that stage is reached, which lets you postpone allocating memory, reading files, querying databases, and other expensive actions that might be in the constructor until the parameters for that stage have been collected from previous stages
Classes aren’t instantiated until you get to the page. But if I click on a previous network node to jump BACK in the pipeline, the state has been kept. So as far as I can tell, if I’m running a Panel Pipeline, the further I go in the pipeline, the more memory I’ll collect since I’ll have instantiated classes for all the pages by the end. Is that correct?