jay@ut-emx.UUCP (Jay Boisseau) (08/17/89)
I have recently upgraded my SE from 1 MB to 4 MB, and I began using MultiFinder immediately thereafter. I have noticed that Moire, which I have been running since before the upgrade, seems to be slower now, and moves in a "herky-jerky" fashion now instead of smoothly. Why is this? Yes, I do sometimes have a two applications open, but that doesn't seem like it should be so much as to affect Moire, especially since neither of them are doing any background processing (Word 4.0 and VersaTerm 3.0, but VersaTerm is NOT downloading). Is this new "effect" (I don't think it is a problem) something anybody else has experienced? Is it due to MF? More memory (I can't see how...)? Jay Boisseau jay@emx.utexas.edu
jay@ut-emx.UUCP (Jay Boisseau) (08/17/89)
I just discovered that the "herky-jerky" motion DOES NOT OCCUR if VersaTerm 3.0 is the "open" application when Moire comes on, but it DOES OCCUR if either Word 4.0 or Finder is the the "open" application. Does this give anyone a clue? Does this mean I am getting a minute performance problem when using Word 4.0? Jay Boisseau jay@emx.utexas.edu
mystone@caen.engin.umich.edu (Dean Yu) (08/17/89)
In article <17218@ut-emx.UUCP> jay@ut-emx.UUCP (Jay Boisseau) writes: >I just discovered that the "herky-jerky" motion DOES NOT OCCUR if VersaTerm 3.0 >is the "open" application when Moire comes on, but it DOES OCCUR if either >Word 4.0 or Finder is the the "open" application. Does this give anyone >a clue? Does this mean I am getting a minute performance problem when using >Word 4.0? Roughly speaking, MultiFinder gives background applications time when the foreground app's GetNextEvent/WaitNextEvent returns a null event. If the foreground app doesn't call GNE/WNE often enough, background applications don't get as much time. For all intents and purposes, screen savers work as background applications. So in short, Finder and Word 4.0 aren't giving enough time to background applications. _______________________________________________________________________________ Dean Yu | E-mail: mystone@{sol,caen}.engin.umich.edu University of Michigan | Real-mail: Dean Yu Computer Aided Engineering Network | 909 Church St | Apt C ===================================| Ann Arbor, MI 48104 | Phone: Given on a need to know basis, and "I am the Merit Host. I speak for | only if you're going to offer me a the bitstream." (In other words, | job... these are my very own opinions; | my employer wants to have nothing |=========================================== to do with them, or me.) | This space available for rent -------------------------------------------------------------------------------
lsr@Apple.COM (Larry Rosenstein) (08/24/89)
In article <45133334.1a5bf@moth.engin.umich.edu> mystone@caen.engin.umich.edu (Dean Yu) writes: > don't get as much time. For all intents and purposes, screen savers work as > background applications. So in short, Finder and Word 4.0 aren't giving > enough time to background applications. I haven't looked at Moire, but based on my experiences with the screen saver I wrote, I would say that the problem is exactly the opposite. Most screen savers seem to hook into GetNextEvent (or the GetnextEvent hook) which isn't called as often if the frontmost application called WaitNextEvent and sleeps. So I think the problem is that the Finder and Word 4.0 are being good citizens and giving background applications the maximum CPU time. The result is that GetNextEvent isn't called as often. Larry Rosenstein, Apple Computer, Inc. Object Specialist Internet: lsr@Apple.com UUCP: {nsc, sun}!apple!lsr AppleLink: Rosenstein1