You can monitor the 'rsz' file or directory (dynamic files) that memresize creates. This will give you an vague idea of how far along it is.
If memresize is extremely slow, it probably means the file we due for resizing long before you got around to it. The better shape the original file, the faster the resize goes in my experience. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 30, 2004 1:25 PM To: [email protected] Subject: RE: [U2] [UD] memresize - checking progress With a larger buffer, memresize can shuffle the data around in memory, then write it the new file. This saves I/O because it can write the file out in whole groups instead of rereading a group to insert each record as it runs through the original file. If the file is larger than the buffer, all the data can't be in memory at once. I don't know what it does in that case, but I imagine it should have some benefit. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Lewington Sent: Thursday, December 30, 2004 11:09 AM To: [email protected] Subject: [U2] [UD] memresize - checking progress Unidata 6+ on various nix/doze platforms. Is there any way to check the progress of a memresize file resize? Sometimes a resize seems to take inordinately long, so I'd like to be able to confirm that it is x% complete and increasing. I imagine the technique would be different for static and dynamic files. Also, does anyone know if and how the [MEMORY buf_size] has any effect on the speed if the buffer is smaller than the file size? I can't see any difference here on a 500Mb static file with an 8Mb and 100Mb buffer. Cheers Simon ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
