Mail Archives: djgpp/2000/10/31/20:46:58
In article <7458-Fri27Oct2000080225+0200-eliz AT is DOT elta DOT co DOT il>,
djgpp AT delorie DOT com wrote:
> > From: dcasale AT my-deja DOT com
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Thu, 26 Oct 2000 21:00:59 GMT
> > >
> > > > My program is, obviously, extremely disk-intensive. I'm caching
> > > > reads and writes with separate 5MB buffers. Could this cause
> > > > the problem?
> > >
> > > No disk I/O should ever affect the system clock.
> >
> > Are you absolutely sure about that?
>
> Yes. The timer interrupt has the highest priority, and so should not
> be affected by almost anything else.
I think I know where the slowdown is coming from now. I tried
temporarily turning off the file compression and encryption to make
sure my program handled it correctly, with the new buffering code
changes, and the slowdown disappeared entirely. Somehow, file
buffering has caused what used to be about a 10% slowdown to balloon to
a 50% slowdown, but it's coming from inside the compression code.
What's annoying is that this code makes _no special interrupt calls_ at
all. It's almost pure C code, in fact, with an interface wrapper class
for the program to call.
Blurgh. -_-
Damon Casale, damon AT WRONG DOT redshift DOT com (remove the obvious)
Okay, this is just plain stupid.
Sent via Deja.com http://www.deja.com/
Before you buy.
- Raw text -