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

Performance comparisons #68

Open
filipwasil opened this issue Mar 6, 2016 · 1 comment
Open

Performance comparisons #68

filipwasil opened this issue Mar 6, 2016 · 1 comment

Comments

@filipwasil
Copy link
Owner

filipwasil commented Mar 6, 2016

The goal is to beat the cocos2dx and ogre3d engines,

Define couple of performance tests.

@filipwasil filipwasil added this to the Version 6.0 milestone Mar 6, 2016
@filipwasil filipwasil modified the milestones: 5.1.1, 5.1 Apr 17, 2016
@filipwasil filipwasil modified the milestones: Rev 6.1, 5.1.1 May 1, 2016
@filipwasil filipwasil self-assigned this May 1, 2016
This was referenced May 13, 2016
@filipwasil
Copy link
Owner Author

If we already have profiling macros, we can now make modular testing. Known test cases:

  • Adding model to tree
  • Adding Animation callback (or other focus callback to engine)
  • Creating model from file
  • First frame draw
  • Second frame draw
  • RAM usage
  • Engine class Construction time

@filipwasil filipwasil removed this from the Rev 6.1 milestone May 13, 2016
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

1 participant