For example, if you store your output in an accumulating data structure instead of hundreds of files that are being kept open, and modularize the process of adding content to the data structure, there's just a little extra planning work to be done to establish a threshold for when data needs to be dumped to a given file so that the given chunk of memory can be reused. It's a matter of striking a balance between the amount of memory consumed and the number of times files must be opened and closed.
In reply to Re: file handle limitation of 255
by graff
in thread file handle limitation of 255
by radnus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |