If I remember correctly then I had a look at that before I set out to do my own experiments and I didn't find something that seemed to match perfectly. However I can do that again and perhaps ask advice from the people over there but I don't think that this is the main issue here.
I think that the job of interning strings can be abstracted in a simple way (A function or two) so that we can worry about the implementation later (My implementation is perhaps attractive because it is simple, it has a reasonable performance and can be activated on a threshold basis so that no option to switch it on or off is needed but I am OK with any other implementation too). My problem (And I think that Sumedh is perhaps struggling with the same issue) is some guidance on how to go about this. We can just look at the patch that was made for the support of shared strings which apparently shares a lot of code witch XSSF and ask ourselves how to make that code use less memory but I suspect that we could perhaps do a much better job if we really understood why the code is the way it is. I would like to have answers to the question like "What are all the other fields in the CTRst class for? Is there a documentation from Microsoft or ECMA that covers this point? Can you point me to the documentation that handles the string externalizing? Looking at the files that Excel produces, things look so straightforward that it seems feasible to rewrite the interning in a few dozen lines. Very likely it isn't but I would like to know why. Thanks, Alex -- View this message in context: http://apache-poi.1045710.n5.nabble.com/Using-MapDB-to-reduce-memory-footprint-of-shared-strings-table-in-SXSSF-tp5717375p5717381.html Sent from the POI - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
