The integration of Persistit in the next version of Sonar (www.sonarsource.org) is a nice improvement. It allows to deal with big amount of temporary data during source code analysis without requiring as much heap memory. So thanks to the Askiban team for this great project.
After some memory profiling, we found that Persistit pre-allocates at least 30Mb of heap mem, whatever the buffer pool configuration. In our case ten buffers of 8192 bytes are supposed to be used (+ an expected overhead of 14%):
Properties props = new Properties();
volume = persistit.createTemporaryVolume();
The increase of 30Mb appears when Persistit is initializing, so indexes are empty at this time. Could you help us to understand this behavior ?
You received this message because you are subscribed to the Google Groups "Akiban User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akiban-user...@akiban.com.
To post to this group, send email to akiba...@akiban.com.
Visit this group at http://groups.google.com/a/akiban.com/group/akiban-user/?hl=en-US.
Thank you for the explanation. It exactly confirms our profiling results.
About the memory constraints, an overhead of 32Mb is accepted, even if you think that it could be reduced regarding our 10 8k buffers. So configuring the size of these journal buffers is not mandatory for our needs.
> Please feel free to send any more questions or comments, and good luck with Sonar.
Thanks, and good luck for Persistit and Akiban too !