One other thing - OGR-25

[Randy Rathbun]

That looks fine to me. Remember that we are in "good blocks" that are more
apt to generate the correct OGR ruler. We are going to see slow times
until we get up in the higher starting numbers.

Also, you will see the first 30% of the block take a mega long time -
hours and maybe even days. Then the client goes into hyper mode and starts
throwing away blocks like nobody's business for the remaining 70% because
it figures out that what it is looking for could not obviously be a good
number. 

OGR-24 did the same thing. When I got blocks like 1-2-3-4-5 it would take
23 hours to churn out a block. When I got blocks like 16-17-18-19-20, it
would take 20 or 30 minutes. 

So just keep on chunking!

Randy Rathbun
randy at rrr.2y.net
http://rrr.2y.net

On Thu, 10 Aug 2000, Dale Beams wrote:

> It is now 6:26 AM ... not much processing here either ...
> 
> [Aug 09 16:21:19 UTC] Automatic processor detection found 1 processor.
> [Aug 09 16:21:19 UTC] Loaded OGR stub 25/1-3-12-9-14-17
> [Aug 09 16:21:19 UTC] 23 OGR packets (23 work units) remain in buff-in.ogr
> [Aug 09 16:21:19 UTC] 0 OGR packets (0 work units) are in buff-out.ogr
> [Aug 09 16:21:19 UTC] 1 cruncher has been started.
> .
> 
> 
> 
> 
>