-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: works slowly #56
Comments
thanks for reporting this bug! Two questions:
|
You're welcome. Thanks for this interesting app!
|
Thank you! :D First of all, try using Anyway, can you send me the content of:
|
By using
The requested logs:
|
Hi, |
Hi |
If you want to improve the performance you can reduce the framerate of the application, here you can find more info. Edit: I closed the issue by mistake, if you need more help then keep asking else close the issue 😄 |
I changed framerate even to 15.0 but the CPU usage is still high (around 40%), is it normal? |
It's strange, could you use a profiler for rust to understand where we're spending so much time? This can be useful: https://nnethercote.github.io/perf-book/profiling.html |
From this graph I can't understand anything. Should be:
|
Anyway, as soon as I can I will try using valgring with callgrind/massive and I will tell something more detailed. |
Steps: cargo install flamegraph
cargo flamegraph |
Perfect, thank you. |
I ran this command ( I'm not sure options are correct or necessary): valgrind --tool=callgrind --callgrind-out-file=callgrind.out --collect-jumps=yes --simulate-cache=yes ./target/release/tgt and the result is in attached file. |
That's perfect! You can use the following command to have a graphical representation of this file
|
As soon as I can, I will do it and then we can discuss on how to fix this problem |
I'm trying to work on new feature but because it's slow I can't debug. |
This night I will see the graphical view of the |
So, this is the graphical view of your I suppose the problem is related to |
Yeah! |
Anyway, we should have a flag that indicate if we need to re-draw the screen, maybe hashing the "current" state? |
Hi! I had the same issue, I was able to fix it by putting the frame rate to 15.0. but my cpu usage still surged up to 20-30% |
We are currently working on fixing this issue. |
Describe the bug
It works very slowly and the CPU is 100%
Reproduction steps
Expected behavior
working smoothly
Logs and screenshots
Method of Installation
Cargo
tgt version
1.0.0
Operating System (including version and architecture)
6.6.44-1-MANJARO
Terminal and Command Line Interface (CLI) (including versions)
No response
rustc and rustup target (including versions)
rustc 1.80.1 rustup 1.27.1
The text was updated successfully, but these errors were encountered: