home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.amiga.hardware:23593 comp.sys.amiga.misc:20373
- Newsgroups: comp.sys.amiga.hardware,comp.sys.amiga.misc
- Path: sparky!uunet!news.smith.edu!sophia.smith.edu!jfieber
- From: jfieber@sophia.smith.edu (John Fieber)
- Subject: Re: Why do Commodities slow down the Amy? (was: How does 2.04 perfor
- Message-ID: <1993Jan23.221208.4690@sophia.smith.edu>
- Sender: root@sophia.smith.edu (Operator)
- Organization: Smith College
- References: <1993Jan15.161155.154120@eratu.rz.uni-konstanz.de> <a4yiXB4w165w@lakes.trenton.sc.us>
- Date: Sat, 23 Jan 1993 22:12:08 GMT
- Lines: 25
-
- hoehle@inf-wiss.ivp.uni-konstanz.de (Joerg-Cyril Hoehle) writes:
-
- >
- > My experience is that only 1 commodity suffices for this and any
- > commodity will do. As soon as your then move your mouse you slow down
- > your (68000) machine. Why does this happen? (Matthew Dillon once said
- > that commodities were using an extremely slow protocol, is this the
- > reason?)
-
- It may be part of the reason, but only part. I think a more
- important component is how how the particular commodity is
- written. If the commodity grabs all messages that come from,
- say, mouse movement and sits on each one for a while, doing lots
- of calculations, sure the system will grind to a halt. I used a
- mouse-blanker for a short time that apparently did this.
-
- With a little thought, it is possible to write commodities that
- impose very little impact on the system performance. I'm sure
- using the commodities system does have more overhead than rolling
- your own input handler but it easier than rolling your own.
-
- -john
- --
- === jfieber@sophia.smith.edu ================================================
- ======================================= Come up and be a kite! --K. Bush ===
-