[11514] in Athena Bugs
Re: MacDiscuss performance issues....
daemon@ATHENA.MIT.EDU (hoffmann@MIT.EDU)
Thu Dec 9 13:26:28 1993
From: hoffmann@MIT.EDU
Date: Thu, 9 Dec 93 13:26:04 -0500
To: mlbarrow@MIT.EDU
Cc: bugs@MIT.EDU, blue-box@MIT.EDU, ij@MIT.EDU
In-Reply-To: mlbarrow@MIT.EDU's message of Thu, 9 Dec 1993 09:08:19 -0500 <9312091407.AA07073@MIT.EDU>
Date: Thu, 9 Dec 1993 09:08:19 -0500
From: mlbarrow@MIT.EDU
... If this is true, it's unnecessary. Take as
an example the Macintosh NNTP client Newswatcher. I use this app and it
performs well under the same configuration. On startup, it reads in the
news file and keeps it memory-resident. When the user quits, it writes the
new news file. All modifications to the news file take place in memory,
resulting in better performance...
The primary drawback of a fully-cached newsgroup file or
discuss meetings file (as you describe it above) is that
if you die in the middle of your session (your machine I
mean) then you've lost ALL your state and are forced to
relive history.
I imagine there could be a middle ground between the two
extremes...
-Ron
