Yes, absolutely - I'm a great believer in a minimum modulo. If I have to copy large files from one to another my preferred method is to drive a load of PHANTOMs with save-lists in parallel. Also useful to drive from a SELECT not a SSELECT so you get a file-sequential order by "chunking" the input list as well so each PHANTOM gets a file-sequential ordered set of input data to process. Large disk caches can futz this idea a little, but it still holds true in general terms.
I think someone else mentioned this as well recently. Regards JayJay On 25 Apr 2012, at 21:28, Wols Lists <antli...@youngman.org.uk> wrote: > On 25/04/12 15:46, John Jenkins wrote: >> We've recently added a new UniData tuneable to udtconfig "UDT_SPLIT_POLICY" >> which can help conserve space when an overflowed dynamic file splits. The >> total size of the contents are not necessarily the same as the physical file >> size. Always worth checking with "guide" and the latest fixes and changes >> for this change if you have a stake here as the new split policy needs to be >> positively chosen. >> >> Regards >> >> JayJay >> > Dunno Unidata, but if you're copying to a dynamic file, would it make > sense to use MINIMUM_MODULUS on the new file? JayJay, you'd know far > more than me about this, but in UniVerse, it makes sense to use it if > your file is not going to shrink and you're creating it specifically to > populate it with a large amount of pre-existing data. > > Cheers, > Wol > > _______________________________________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
