Revision: 1170
Author: tim.bunce
Date: Fri Mar 12 07:29:59 2010
Log: Using SQLite for reporting on profile data might be a good direction...
http://code.google.com/p/perl-devel-nytprof/source/detail?r=1170
Modified:
/trunk/HACKING
=======================================
--- /trunk/HACKING Wed Feb 24 02:50:05 2010
+++ /trunk/HACKING Fri Mar 12 07:29:59 2010
@@ -399,3 +399,11 @@
Currently lvalue subs aren't profiled when use_db_sub is in effect.
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2010-02/msg00824.html
+Idle conjecture: perhaps loading the profile data into an SQLite database
+would be a better approach to reporting.
+(An nytprofimport utility could read an nytprof.out and write an
nytprof.db)
+Then, rather than hand-crafting inflexible data structures we could use SQL
+(or, say, DBIx::Class) to return relevant data. Would also provide another
+route for other data sources (languages/tools) to be included in a report.
+Could also simplify: comparing profiles, merging profiles, ...
+Any volunteers to explore writing an nytprofimport for SQLite?
--
You've received this message because you are subscribed to
the Devel::NYTProf Development User group.
Group hosted at: http://groups.google.com/group/develnytprof-dev
Project hosted at: http://perl-devel-nytprof.googlecode.com
CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf
To post, email: [email protected]
To unsubscribe, email: [email protected]
