TeensyMud - 'A ruby mud server.'

Subject: Released 2.7 status
Subject: Released 2.7 status
Author: Tyche
Posted: 01/16/2006 03:56PM

I was all set to go for a weekend release, but I discovered some problems. They will take a few days to iron out. There's over a thousand lines of new code with this release which is about the average between releases do far. It should complete another one of those kernel bricks I've been talking about, Storage, (more or less).



reply
Subject: Released 2.7 status
Author: Tyche
Posted: 01/16/2006 10:50PM

Tyche wrote:
> I was all set to go for a weekend release, but I discovered some problems. They will take a few days to iron out. There's over a thousand lines of new code with this release which is about the average between releases do far. It should complete another one of those kernel bricks I've been talking about, Storage, (more or less).
>

Problems solved. We should have liftoff soon.

This is TeensyMud with the stock Diku alfa database loaded.
---* Database Statistics *---
  Rooms   - 657
  Players - 1
  Objects - 253
  Total Objects - 911
  Highest OID in use - 2439
---*                     *---

----------* Cache Statistics *----------
cache marks               : 946
database reads            : 3156
cache mark misses         : 10
reads                     : 3662
database writes           : 918
writes                    : 1
cache read hits           : 506
cache size                : 161
cache noswap              : 1
----------*                  *----------


----* Memory Statistics *----
  Rooms   - 177
  Players - 1
  Objects - 61
-----------------------------
  Strings - 59154
     size - 1592776 bytes
  Other   - 9033
-----------------------------
  Total Objects - 68426
----*                   *----


Mucho cache thrashing above and slow on the the routines that traverse the entire database. However that's the point, you can at least get it running where memory is tight.






reply
Subject: Released 2.7 status
Author: Massaria
Posted: 01/17/2006 10:17AM


> Problems solved. We should have liftoff soon.

Trajectory.... check
Pitch... check
Roll... check
We're on course cap'n!


> This is TeensyMud with the stock Diku alfa database loaded.

Heh. Cool Feature Tyche. Think the 13 year death spiral will pick up speed now? ;-)

I assume this is done with the dbload/dbdump files? Are they useful for anything else?
I don't mean to be critical - I think it's a brilliant move - but once you settle for a dbtype to use, yaml in my case, is there any use for dbload/dumb?
Are the other types faster, or take up less space or something else?

Good going with the deep copy thing and @memstats too.

Anyways, back to checking it out :-)
Mass.

______
EDIT:

I see you've made good of your threat with those properties.
Could you elaborate a bit on the gains and use of it (as opposed to attr_accessor)?

Thanks.

reply
Subject: Released 2.7 status
Author: Tyche
Posted: 01/17/2006 11:54AM

Massaria wrote:
>
> > This is TeensyMud with the stock Diku alfa database loaded.
>
> Heh. Cool Feature Tyche. Think the 13 year death spiral will pick up speed now? ;-)
>
> I assume this is done with the dbload/dbdump files? Are they useful for anything else?

MudlibReader is the utility that reads other mud's databases and creates TeensyMud databases. The dbload/dbdump utility programs just load or dump the dbm's to and from yaml.

For example:

./dbload.rb -t gdbm -i db/testworld

That will build db/testworld.gdbm from db/testworld/yaml, then you change your configuration file to use dbtype :gdbm.

If you want to run regular backups of your database to yaml you'd do something like:

./dbdump -t gdbm -i db/testworld -o db/testworld-060111-1124PM-backup


> I don't mean to be critical - I think it's a brilliant move - but once you settle for a dbtype to use, yaml in my case, is there any use for dbload/dumb?
> Are the other types faster, or take up less space or something else?

If you are using yaml as the backend, you can ignore the utilities and the dbm's. Just make sure the configuration file has yaml as the dbtype. If you decide at some point to use a dbm then you can use the utilities to build one from your yaml file. The tradeoffs are memory and speed. I haven't done any real measurements.

> I see you've made good of your threat with those properties.
> Could you elaborate a bit on the gains and use of it (as opposed to attr_accessor)?

Well there's this, PropertiesModule.



reply