Modify a text file without make a copy
in [VbScript]
|
From: Reventlov on 27 Feb 2010 16:51 Il giorno Fri, 26 Feb 2010 16:41:55 -0500, "Todd Vargo" <tlvargo(a)sbcglobal.netz> ha scritto: >How many bytes is a "kio"? In French, byte is "octet". It's a word which comes from "eight" -- Giovanni Cenati (Bergamo, Italy) Write to "Reventlov" at katamail com http://digilander.libero.it/Cenati (Esempi e programmi in VbScript) --
From: mayayana on 27 Feb 2010 18:00 > 1 kio = 1024 bytes > 185 kio = 189440 bytes 700 files is a lot to process, but 185 kio is not very big. It might be worth trying it with FSO to see how long it takes. Maybe it will cause a little bit more disk wear, but even with the slow and inefficient FSO it should be very fast to open/edit/save a file of that size.
From: Todd Vargo on 28 Feb 2010 00:25 mayayana wrote: > >> 1 kio = 1024 bytes >> 185 kio = 189440 bytes > > 700 files is a lot to process, but 185 kio > is not very big. It might be worth trying > it with FSO to see how long it takes. Maybe > it will cause a little bit more disk wear, but > even with the slow and inefficient FSO it > should be very fast to open/edit/save a file > of that size. Even if all 700 files are modified on a daily basis, the drive heads still have to move over the platter. No doubt, the drive will see more activity just by using your web browser. -- Todd Vargo (Post questions to group only. Remove "z" to email personal messages)
From: mayayana on 28 Feb 2010 09:14 > Even if all 700 files are modified on a daily basis, the drive heads still > have to move over the platter. No doubt, the drive will see more activity > just by using your web browser. > I'm no expert on hard disks. And with XP+, if junk services like indexing are not turned off, the disk seems to work almost constantly. On the other hand, I figure it doesn't hurt to keep the issue in mind and try not to stress the disks any more than necessary. That's typically the first thing that goes in a PC. The moving parts don't necessarily need to be moving all the time, especially when using a web browser. I often find that I load 2 or 3 articles into a browser, and by the time I finish reading them the disk has long since "gone to sleep". Once the page is loaded it's all usually in RAM. Likewise with writing or coding. A lot of time can pass where the disk doesn't *need* to be doing anything at all.
From: Al Dunbar on 1 Mar 2010 20:04
"mayayana" <mayayana(a)nospam.invalid> wrote in message news:O$01nAIuKHA.5148(a)TK2MSFTNGP04.phx.gbl... > >> Even if all 700 files are modified on a daily basis, the drive heads >> still >> have to move over the platter. No doubt, the drive will see more activity >> just by using your web browser. >> > > I'm no expert on hard disks. And with XP+, > if junk services like indexing are not turned off, the > disk seems to work almost constantly. On the > other hand, I figure it doesn't hurt to keep the > issue in mind and try not to stress the disks any > more than necessary. That's typically the first thing > that goes in a PC. If this is the case, then I assume that you never defrag your hard drive? Or run diagnostics to monitor its health? I am all for efficiency in coding, but this doesn't sound like a disk breaking application. He is already running scripts to append to these files from the eventlog, so it's not like these large files are full of important information that is never processed. I still suspect, however, that there might be some completely different ways to accomplish what it is he is trying to do. /Al > The moving parts don't > necessarily need to be moving all the time, > especially when using a web browser. I often find > that I load 2 or 3 articles into a browser, and by > the time I finish reading them the disk has long since > "gone to sleep". Once the page is loaded it's all > usually in RAM. Likewise with writing or coding. A lot > of time can pass where the disk doesn't *need* > to be doing anything at all. > > |