Skip to content
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

Profiler: usability ideas #5682

Closed
Zylann opened this issue Jul 13, 2016 · 4 comments
Closed

Profiler: usability ideas #5682

Zylann opened this issue Jul 13, 2016 · 4 comments

Comments

@Zylann
Copy link
Contributor

Zylann commented Jul 13, 2016

After testing a bit the profiler, I have a few ideas to improve its usability:

  • Ability to focus spikes more easily. Half of performance bottlenecks can be seen as spikes, and focusing them in the profiler is currently a bit tedious since you have to be pixel-perfect when clicking on the graph.
    Could we have zoom or something allowing easy precision?
  • Functions taking most time should be ordered first instead of last, because they are the point of profiling. I see I can click on the headers but it does nothing particular.
@akien-mga
Copy link
Member

Not critical for the upcoming 2.1, so moving to the next milestone.

@akien-mga akien-mga modified the milestones: 2.2, 2.1 Jul 27, 2016
@Zireael07
Copy link
Contributor

Being able to order the functions by time spent would massively improve the usability of the profiler. (As simple as making the click on the header sort decreasing/increasing)

@Zireael07
Copy link
Contributor

Bump. Zooming in and ordering are needed.

Also in the monitors tab, what is the range of values for fps? It's weirdly difficult to see the difference between 15 and 30 FPS.

P.S. Where should I look if I want to improve those things?

@Calinou
Copy link
Member

Calinou commented May 15, 2021

Note: Ordering functions from most to least expensive has already been implemented in 3.1 and later by #25354.


Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated [Godot Improvement Proposals (GIP)](https://github.com/god
otengine/godot-proposals) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.

The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.

If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants