On Thu, 9 Dec 1999, Richard Hartman wrote:
> > >5) I looked at the count and it was 395,000. Some time later it was
> > >400,000. Then a few minutes later it was back to 390,000. Very
> > >irratic.
> >
> > It's not a bug, it's a feature! The latest version of POSE
> > has something
> > called "gremlin hordes", which means it switches between
> > several different
> > gremlins. If the switching depth is set to 10000 (which I
> > believe is the
> > default) POSE runs each Gremlin for 10000 events and then
> > switches to the
> > next.
> >
> > This is probably what happened in your case. POSE ran events
> > 390000-400000
> > of gremlin #0 and then events 390000-400000 of gremlin #1.
> > That is why the
> > counter was seemingly set back. (If you studied the dialog
> > box carefully you
> > would notice that the gremlin number in the upper right
> > corner changed.)
Maybe but several other things cannot be explained.
1) When I tested the app on 2.x POSE, I would occasionally get
"read from low memory" errors. I have been running POSE for
3 days now and NO errors at Gremlin 0, 1, 2. I doubt that my
app is bullet proof and I have all logging options on.
2) To run 1,000,000 Gremlin operations does not take over 12 hours
on my PC. After 12 hours the count was only up to 400,000. I had
Gremlin test set to only do 1,000,000 tests. But it would never stop.
3) At one point I stopped the tests and could not Restart the test. I
could 'Step' but could not 'Restart'.
These seem like problems. It would be nice to believe that I had
absolutely NO errors (or problems) but I doubt that this is the case.
Especially when 2.x would occasionally show "low memory accesses".
Mike
> > // Niklas
> >
>
>
----------------------------------------------------
Shoot-to-Win
Protect the 2nd Amendment
----------------------------------------------------
