[Home] [Groups] - Message: [Prev in Group] [Next in Group]
18992: Re: [MUD-Dev] Re: TECH: Distributed Muds
[Full Header] [Plain Text]
From: Brian Hook <bwh@wksoftware.com>
Newsgroups: nu.kanga.list.mud-dev
Date: Wed, 25 Apr 2001 18:37:02 -0700
References: [1] [2] [3] [4] [5] [6] [7] <-newest
Organization: Kanga.Nu
At 05:07 PM 4/25/01 -0700, J C Lawrence wrote:
> Simple traversal is not really the problem. The underlieing problem
> is fragmentation and resultant thrashing of the OS page cache.
Simple traversal at the limit is still going to cause a whole bunch of
swapping irrespective of page cache thrashing.
But that actually leads to another really gnarly problem, which I
assume that MUD developers have a bunch of experience with, and that's
dealing with memory fragmentation in general. Obviously a bunch of
calls to new/delete during the run time of a server (or a client if
someone stays logged in for days at a time) isn't going to be
particularly feasible.
I'm curious how that's handled in the real world. The obvious
mechanism is to have fixed allocation pools for different object types
and to manage your own memory using handles that allow compaction.
Brian Hook
_______________________________________________
MUD-Dev mailing list
MUD-Dev@kanga.nu
https://www.kanga.nu/lists/listinfo/mud-dev