PECL account for publishing an extension
| From: | Constantin-Emil MARINA | Date: | Fri, 31 May 2013 12:35:51 +0000 |
| Subject: | PECL account for publishing an extension | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-10731@lists.php.net to get a copy of this message | ||
Hi all,
My name is Dinu MARINA, working for EXTEON, a small PHP development company
loated in Bucharest, Romania.
About one year ago we forked off XHProf profiler (or rather, kept meta-code
and timing functions, rewrote the rest, so this is NOT a maintenance build)
to provide recursion handling and better performance and KCachegrind output.
The v1 version can be found here:
http://www.exteon.ro/en/products/php-tools/web3tracer
Now we have made and are in the process of documenting v2 which
(re)introduces new features:
- Memory usage profiling
- Switch back to native PHP profile data and use PHP writer
wrappers to generate output files
- Uint64 counters for larger data support
We would like to publish this extension on PECL to gain visibility and
community feedback. There are a number of performance monitoring tools that
could benefit from the recursion handling rewrite. I wuld ask you to review
the opportunity of this and if so grant an account on PECL.
We mostly tried to keep consistent with the XHProf coding style (consistency
over standardization), so if the coding style does not thoroughly conform to
your guidelines, that can be managed in time.
I would also like to ask a question (maybe this is not the right place, but
it's a good starting point): for the profiler, it would be very useful to be
able to hook into the zend engine memory handling functions, especially:
- emalloc, efree etc. for timing and quantization of memory
requests; the peak and current memory usage are not great indicators for
memory performance
- the GC sweep for timing the GC operation
Would this be something to request as a feature on bugs.php.net? Or should
it be discussed some place else, having rather to do with a design decision.
Note: This message was sent before and man-handled by the list bot (required
confirmation), but still doesn't appear on the mailing list, and no reply
received. Sorry if this message is in duplicate. If someone sees this,
please reply directly to from address, we can't confirm the email is going
where it's supposed to.
Thanks, waiting to hear from you, if you're in the neighborhood drop a SYN,
Dinu