$Id: README,v 1.2 1997/08/12 00:13:51 tiggr Exp $

This is the README for gcdo, the Distributed Objects Garbage Collection
test and example.  At the time of writing (Tue Aug 12 1997) GCDO performs
1000 remote invocations, each time passing a new proxy to the other side,
which will then be messaged back, etc.  The number of invocations can be
changed by providing a number on the command line.

You can view the garbage collection by providing any combination of the
`:gc-stat' and `:gc-debug 1' command line arguments.  Run `./gcdo.debug
:help' for more library handled command line arguments.  Giving `:rt-inst'
will dump the number of live objects of each class at program exit, and
you can verify that indeed the local and remote proxy objects are being
cleaned up.

Here are two examples:

(gdb) run 1000 :gc-stat :gc-exit :gc-pth 1000 :rt-core
gc: runs: 30 completed: 30
total: alloc: 28790 dealloc: 27926 remaining: 864
(gdb) run 1000 :gc-stat :gc-exit :gc-pth 10000 :rt-core
gc: runs: 4 completed: 4
total: alloc: 28782 dealloc: 24171 remaining: 4611
(gdb) 

It shows that these particular remote invocations (a simple method with
one object argument which in this example always results in the creation
of a proxy) will cost about 28 object creations per invocation.  It also
shows that with garbage collection being run less often (second example),
the remote proxy objects do not get a chance to become garbage _and_ have
their connection inform the other side of this fact.
