[Fwd: Lazy-lock and gnuclients use a lot of cpu time.]

please use xemacs-beta for bugs. do you see the same thing if you create 3 or 4 frames using C-x 5 2 and edit files with them, or only when you use gnuclient? -------- Original Message -------- Subject: Lazy-lock and gnuclients use a lot of cpu time. Date: Fri, 10 Aug 2001 15:29:27 -0500 From: Paul Cheng <ptc(a)sgi.com&gt; To: ben(a)xemacs.org Hi Mr Wing, I noticed that in xemacs-21.4.4, using a combination of gnuserv, gnuclient and lazy lock causes xemacs to use a lot of cpu time. I am running xemacs on an SGI indy running irix6.5.12. Here is the detail: 1. I use the sample.init.el from the distribution as init.el. This has lazy-lock enabled. 2. I start xemacs and then start gnuserv with the gnuserv-start command. 3. I use gnuclient to start editing some files. For example, gnuclient -q .profile After the new frames pop up on my screen, I let them sit idle. When I edit only one file, xemacs uses about 8% of the cpu time. If I start two gnuclients, the cpu time jumps to about 20%. If I start a third gnuclient, the cpu time jumps to about 25%. If I start a fourth gnuclient, the cpu time jumps to about 35%. If I turn off lazy-lock, then the cpu time remains at about 0.8% no matter how many gnuclients I use. If I enable lazy-lock and do not use gnuclients, then each xemacs process uses about 0.8% of cpu time. Since the increase in cpu time is so huge when both lazy-lock and gnuclients are used together, I am just wondering if this is a bug. Thanks. Paul Cheng.