On Mon, 2005-12-19 at 18:35 -0500, John Siracusa wrote: > If the number of iterations is fixed, you get a usable wallclock time in the > results.
The danger here is that cmpthese does not use that, so the compare option is misleading. I got bitten by that once, assuming that the :hireswallclock option would change what cmpthese compares. > Anyway, the fact that working around the feature/performance deficiencies of > a particular ORM is "common practice" is hardly a convincing endorsement :) > In the particular case of fetching related objects, many ORMs do include > this feature, and users like it and use it. I completely agree. That's why I brought it up -- I'm interested in seeing the performance penalty (in extra queries) that Class::DBI has in this regard highlighted. - Perrin ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
