Return to Question

The text file consists of 240 000 lines, each of which contains one word, which is read into a String. Each is then parsed into a char[] to access the individual characters, each char is then placed into the tree separately.

The text file consists of 240 000 lines, each of which contains one word, which is read into a String. Each string is then parsed into a char[] to access the individual characters, each char is then placed into the tree separately.

Android puts a limit of 16-26MB of RAM usage per application if I am correct. When my application runs it consistently hits this mark. It takes around 47 seconds to initialise the Vocabulary object and about 1/10 of a ms to see if a word exists in this Vocabulary. Right now I am afraid that I made a mistake by implementing the RadixTree data-structure since it costs too much RAM and takes way too long with 47 seconds...

Android puts a limit of 16-26MB of RAM usage per application if I am correct. When my application runs it consistently hits this mark during the initialization of the large Vocabulary object. It takes around 47 seconds to initialize the Vocabulary object and about 1/10 of a ms to see if a word exists in this Vocabulary. Right now I am afraid that I made a mistake by implementing the RadixTree data-structure since it costs too much RAM and takes way too long with 47 seconds...

My idea was to load the object to later restore it. However this is even slower, loading an object took about 5x longer. Oh dear.