On Mon, Nov 01, 1999 at 03:52:19AM +0100, Hrvoje Niksic wrote:
Have you tried measuring startup speed of XEmacs?
No. But I'm still in the <1s area for startup.
How long does it take to relocate the data?
Not much, obviously. Incidentally, a missing feature (which will be easy to implement
once I consider the rest of the system stable enough because it needs some support in the
build process which will have to call temacs twice, once for dumping
, once for relocating) is pre-relocating the data to the address the initial mmap
() puts the file to. I'll do some tests, but I have no reason to think that it should
change between subsequence invocations of the same xemacs
.
Is the mmap()ed data shared between XEmacs processes?
Implicitely, which means not at all.
Implicitely, because any decent system does copy-on-write. This includes all modern
unices
, at least.
None at all because:
- the relocating process writes to most of the pages
- the garbage collector writes to the remaining ones
So, in order to have sharing we need the pre-relocation and a smarter gc
(which is probably going to come with Jan's allocator model).
Ouch, there still are some nasty bugs in the pdump. Active regions setup is lost
. Same for auto delete selection. M-q breaks lines in all the wrong places
. And loses the line length, too, it seems, while that may only be a side effect of not
knowing where to break the line.
Isn't that mail cute once filled by a pdumped XEmacs? ;-)
OG.