Hi Ken,
Follow up on test results for the 3 scenarios. I added the OS mem usage in each case (which is the real issue). The last option seems to be a little faster (
<$fh> ) but mem usage is similar to Memory::Usage shows.
I am going to try the 'slurp string' as the next option as suggested by BrowserUK.
Also interesting that using the reference (T2) uses 15% more RAM.
T1: size(\@data): 177490392 total_size(\@data): 183760484
+8
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6569 xxxxxxx 25 0 6355m 6.0g 1592 R 100.0 51.5 0:46.67 perl
T2: size($data_ref): 177490392 total_size($data_ref): 183760484
+8
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6603 xxxxxxx 25 0 7208m 6.9g 1592 R 100.0 58.6 0:51.38 perl
T3: size($data_ref): 177490392 total_size($data_ref): 175598464
+9
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
6625 xxxxxxx 25 0 6315m 6.0g 1592 R 100.0 51.2 0:47.73 perl
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.