Larry Smith <lsmith(a)cio2000.eds.com> wrote:
A dired over the network is very very bad. I find the following
useful, especially combined with drag-and-drop.
I don't see a problem with dired in XEmacs & network drives. Can
you elaborate?
On a P150 MMX laptop running Win95 OSR2, doing a dired of
c:\windows\system (~1120 files) takes around 10-11 seconds.
On the same system, doing a dired of a network drive (~950 files)
takes 9-10 seconds. The lan card is a slow PCMCIA (non-cardbus) 10BT
card. The network drive is on an NT box running 4.0sp3, and the
remote directory scanned is c:\winnt\system32 (on the NT box).
Both of these times are comparable, and so I don't see any
problem. Dired would run even faster if I compiled XEmacs without
debugging turned on.
However, this is with XEmacs debugging turned on, which slows down
XEmacs, but with the dired-in-C code enabled. This is also with some
dired patches (for performance increases) that I recently submitted to
the dired maintainer, but these patches affect all uses of dired, and
would make no difference between a local or network drive.
-- Darryl Okahata
Internet: darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.