|
in reply to Efficiency and Large Arrays
If you have the memory to spare and efficiency is of utmost
importance, then by all means load as much as you can into memory.
If memory is tight or you can deal with longer runtimes
(and more disk IO) then store the data in some
sort of persistant storage (SQL DB, hash tied to a DBM file, etc...).
This is the classic space vs. performance tradeoff. You are
going to have to decide which is more important to you in
your particular circumstances. |
RE: RE: Efficiency and Large Arrays
by Kozz (Friar) on Jul 23, 2000 at 01:50 UTC
|
Well, it all gets loaded into memory (currently), which is fine by me. Let it gobble the memory if it's necessary. But the issue is that the entire process is still too slow.
*scratches head* | [reply] |
|
|
I would recomend using a profiler like the Devel::DProf
module to profile your code and try and isolate the bottlenecks.
| [reply] |
|
