Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m debugging and fixing a complex app, that works with a huge Java object (~250M).
I’ve created this object with another program. Currently I use XStream to load and save this object from the hard drive, but it takes more than a minute to parse it.
It slows down the development process.
Is JAXB faster? Are there any other ways to load and save this huge thing?
In that case I would Serialize the data which will make it smaller and faster. You can Externalise key classes to improve the speed further. Here are some test I did more recently Protobuf vs Thrift vs Java Serialization Its the same benchmark as kovica suggest but run more recently on newer hardware/software.
If you need to go faster you can use memory mapped data. This is much harder to work with but you can’t beat the performance. You can load 250 MB is tens of milli-seconds if the data is already in disk cache. If not you will be limited by the speed of your drive e.g. a slow 40 MB/s drive will take about 8 seconds.
A library I wrote uses memory mapped files is Java Chronicle