Clear questions and runnable code get the best and fastest answer |
|
PerlMonks |
Re (tilly) 1: Mega XSLT Batch job - best approach?by tilly (Archbishop) |
on Jan 22, 2002 at 18:23 UTC ( [id://140662]=note: print w/replies, xml ) | Need Help?? |
Given what you would describe I would plan on, one way or
another, winding up with LibXSLT inlined in Perl. But before coding, my next question is how many parallel processes you can profitably run. This is a question of whether you are bound on I/O or CPU. If CPU, then it is generally not worthwhile to run more processes than you have CPUs. If I/O then it depends on your hardware, and what fraction of time is CPU. The last time I tested an I/O bound job, 7 worked best for me. YMMV. Next try a run of 50-100 pages with LibXSLT, and see if you have a serious memory leak. If memory usage stays flat, then I wouldn't worry about it. If it is clearly leaking but doesn't wind up at a worrying level, note that. If it leaks unacceptably, figure out how many you can do in one "batch". Now you have cases:
Good luck, and tell us how it went.
In Section
Seekers of Perl Wisdom
|
|