Hi,
I’m experiencing quite some unpleasant issue with the workspace for testing app. Indeed, as the app is quite heavy with about 1000 parameters, I could not test it in the Development workspace. Each time I made a change, I have to publish the app so as to be able to test, and it’s not practical at all. And even in doing that, I often got an error saying the app cannot be reached actually. As this error is not systematic, I have no idea where it comes from, but I have a doubt on the memory or running time limit of the workspace.
Have you any ideas?
Thanks,
Huy
Hi @vuquochuy ,
Thank you for reaching out. I think this is caused by a limit that we have set on the parameters (1MB if I am not mistaken). It would be good to understand if it indeed is this parameter limit. Could you check that for me?
As a rule of thumb I think it’s fair to say that if your app cannot be run in your development workspace (using your own pc’s resources), running it in production will also be very difficult if not impossible.
Most laptops and/or pc’s you are using for your local development have more RAM, a faster CPU, etc. than the virtual machines running your app in production.
In your list of 1000 parameters, are there also files that were uploaded, or big tables present?
Hi @mslootweg,
Thank for your reply. Please tell me how to check the total memory used by the parameters? Is it pure Python memory? If it’s the case, just to check the memory used by params?
Thanks,
Huy
Hi @rweigand,
For more details: I create an entity starting with a certain type. Once validated, I need to change the type of this entity. But as changing the type of an entity is not possible in Viktor, I have to create another entity with the new type, based on the parameters of the previous one, and then delete the latter. Now I want to open the new entity, impossible locally in my computer! But when I publish the app, it works normally. It’s very embarrassing as each time I change the code, I cannot see it locally but need to publish. My computer is a pro workstation so no issue with that. There are some files uploaded with parameters, but they are not huge. What is the limit for that?
Thanks,
Huy
I believe the memory to check is the JSON that gets sent and retrieved with every trigger event. You could either dump your params in a JSON file, and see how big that is, or you could inspect the Network tab of your browser, where you will see that params JSON in the requests tab.
