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

Improvements: Using a debugger to measure performance #11

Open
GoogleCodeExporter opened this issue Mar 2, 2016 · 2 comments
Open

Improvements: Using a debugger to measure performance #11

GoogleCodeExporter opened this issue Mar 2, 2016 · 2 comments

Comments

@GoogleCodeExporter
Copy link

I need to use a debugger (or something) to measure the performance of the
class methods. I am too unsure to decide whether I use array_slice or a for
loop to resize an array which is possibly too large to handle.


Original issue reported on code.google.com by [email protected] on 10 Sep 2009 at 4:17

@GoogleCodeExporter
Copy link
Author

Introducing Xdebug: I've made the first tests using Xdebug as memory 
monitoring. Creation of files mainly poses 
threads to the object which will be created before sent into the file. I am 
currently working on version 1.2 and 
will post key findings and performance analysis before the release.

Original comment by [email protected] on 29 Sep 2009 at 6:41

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 29 Sep 2009 at 6:42

  • Added labels: Milestone-Release1.2

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