We have developed an ontology edit function that runs fine when not in a scenario, but non-determinisitcally times out when being executed in a scenario. The functions are heavily reliant on object set loads. I was wondering if loads are slower in a scenario than in the normal ontology?
Yes, with the current architecture scenarios may be slower, as every scenario change has to be applied onto the selected objects, so performance depends on the amount of changes from the main branch your scenario has on the loaded objects. This may be optimized in the future as we consider more solutions