Replies: 1 comment
-
|
Obrigado por compartilhar esse caso tรฃo detalhado! ๐ Tambรฉm enfrentamos desafios semelhantes com projetos grandes em Robot Framework, entรฃo sua anรกlise รฉ valiosa.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello all,
Weโre running into performance and memory issues when using RobotCode on large Robot Framework projects.
Iโve uploaded a dummified version of our real project here:
๐ https://github.com/petrieh/dummified-robot
Itโs about 460 MB of .robot and .resource files, trying to follow good design practices (no global resources, modular keywords, clear hierarchy). Even though it contains only simple keywords and calls, RobotCode takes ~30-40 minutes to analyze it and uses around 6 GB RAM, which isnโt freed afterward. The real project takes roughly 3 hours and uses up to 12 GB RAM.
This makes RobotCode hard to use in Dev Containers, since it seems to reanalyze everything each time the container starts, even when nothing changed. The extension data is mounted to the container and kept intact between restarts.
โ Questions
Iโm happy to help investigate or fix the issue โ Iโd just need some guidance on where to start inside the RobotCode codebase.
Beta Was this translation helpful? Give feedback.
All reactions