That was really good! It partly answers a nagging question I had after doing those speed comparisons between your Math::3Space vector calculations and doing it in PDL, which is still a bit slow in transitioning between Perl-land and C-land. One thing I know, thanks to using
cachegrind, is that looking up a PDL object's
pdl* spends a lot of time in
hv_common, from
sv_derived_from via
isa_lookup, as called by the
typemap-used
pdl_SvPDLV.
In your opinion, would using this Perl magic scheme be quicker? And if so, does any hero feel like PR-ing (or just commenting some part-way code on https://github.com/PDLPorters/pdl/issues/451, the PDL performance issue) to make PDL-pointer-getting go quicker? (That issue has my previous research that found the hv_common stuff, and also links to the Math::3Space discussion issue)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.