[Chicago-talk] Limiting system impact.

Steven Lembark lembark at wrkhors.com
Wed May 9 14:04:54 PDT 2007


> Nice may not be a nice solution. Try if the file
> can be chopped down to small pieces

Put it another way: nice-ing a memory hog just
guarantees it will hog the memory for the longest
possible time.

Chunking or serializing the data, using intermediate
data files, or pre-sorting the input will usually
help get the bulky work done sooner. For example,
a frequent reason for storing an entire file in
core is to compare rows to one another. In this case
pre-sorting the data may allow for a window of rows
rather than the entire file.

Aside from that, Perl doesn't give you direct
control over core (aside from designing terse
data structures) or CPU since it is a virtual
machine and doesn't control the real memorh or
CPU scheduling.

-- 
Steven Lembark                                         85-09 90th Street
Workhorse Computing                                  Woodhaven, NY 11421
lembark at wrkhors.com                                      +1 888 359 3508


More information about the Chicago-talk mailing list