-------------------------------<br />you can't move ahead, unless you try for it.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
-------------------------------<br />you can't move ahead, unless you try for it.
Originally posted by Akhil Jain:
What is the best way to serialize objects (the most efficient, keeping performance in mind), if we have to serialize around 20,000 Objects per sec to a file? and that too....a strategy which doesn't uses much of a synchronized blocks or methods (because they have their own performance bottlenecks) and allow multiple threads to persist objects in the same file?
apigee, a better way to API!
-------------------------------<br />you can't move ahead, unless you try for it.
-------------------------------<br />you can't move ahead, unless you try for it.
Originally posted by Akhil Jain:
Because channel will automatically take care of Multiple Thread scenario and moreover, using synchronized startegy will have a nice perfromance hit with so many Objects being serialised and written concurrently by different threads in single file.
apigee, a better way to API!
-------------------------------<br />you can't move ahead, unless you try for it.
Originally posted by Akhil Jain:
because i am still getting StreamCurruptedException while deserializing the objects from file.
Originally posted by Akhil Jain:
Strategy for writting multiple objects to same file with different threads (or may be single thread, which gets event objects from different threads to be serialized in a file), can be decided later on.
apigee, a better way to API!
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |