CompuServe Thread

Forum unknown · Programming

#MODULA-2

3 messages in this thread
#37623From: Steve FaiwiszewskiOct 28, 1986 8:38 PM
I haven't looked at this, but it might be that the new release does I/O in a slightly different manner. Why don't you try to write the data file to another drive (or RAM). That should cut down on seek time tremendously. Then, after you're done writing to the data file, you can copy it to its correct location. – Steve –
#37696From: ED MITCHELLOct 29, 1986 2:54 PM
We have been working for three days now on the problem. We have narrowed the problem down to reading the data. We have tried all the different I/O styles (Streams,DOSFiles,InOut). We have also tried to buffer the Input and Output ourselves. At some point in the program the reads start to grind away everytime the buffer needs to be refilled. We have had one solution (Ha!!) to get around the problem. In the course of debugging the program to find out where and what was causing the slowdown, we wrote to the terminal everytime a line was read in from the text file. For some strange reason this appeared to solve the problem. The extra output to the terminal is unwanted, so we tried sending these messages to a file, and the same problems arose again. We have no idea why Terminal output would affect Disk Input. Thanks for your suggestion. We'll give it a try.
#37696From: ED MITCHELLOct 29, 1986 2:54 PM
We have been working for three days now on the problem. We have narrowed the problem down to reading the data. We have tried all the different I/O styles (Streams,DOSFiles,InOut). We have also tried to buffer the Input and Output ourselves. At some point in the program the reads start to grind away everytime the buffer needs to be refilled. We have had one solution (Ha!!) to get around the problem. In the course of debugging the program to find out where and what was causing the slowdown, we wrote to the terminal everytime a line was read in from the text file. For some strange reason this appeared to solve the problem. The extra output to the terminal is unwanted, so we tried sending these messages to a file, and the same problems arose again. We have no idea why Terminal output would affect Disk Input. Thanks for your suggestion. We'll give it a try.