[mkgmap-dev] Memory limits for mkgmap and splitter

Thu Jul 2 19:52:16 BST 2009

2009/7/1 Steve Ratcliffe <steve at parabola.demon.co.uk>:
> Hi
>
>> In PERL it is builtin "tie" functionality, I have, however, no idea
>> what is the used data structure in mkgmap and splitter and how to
>> translate the trick into Java.
>> If you think that the change is trivial and point me to the critical
>> section I might see if I get it implemented.
>
> I was originally going to use berkeley db for the splitter and
> if you go back to revision 3 in subversion there is
> some code that uses the BerkeleyDB java edition.
>
> I gave up on it because it seemed like it would take vastly more
> disk space than the planet file and was much slower than I was expecting
> or hoping.  But I didn't persevere that much before switching to
> the current open hash map implementation, so I'm not saying that it is
> unworkable.
>
Could you please tell me which "Map" would have to be "reimplemented"?
There was a lot of changes (and file deletions) since version 3.

Could you explain why you write that
"There is a maximum of 255 output files. This should anyway be enough
with the current amount of data."
?

Thanks,

Paul

-- 
Don't take life too seriously; you will never get out of it alive.
                                        -- Elbert Hubbard