Re: [Libmesh-devel] [Libmesh-users] System::read_serialized_data performance

2012-10-06 Thread David Knezevic
Hi all, I wanted to pick up on this thread again. I gather that a change was made to the block size in read_serialized_data that led to a significant speedup for the use case that Jens was looking at. But this is still a bottleneck for a lot of the reduced basis code, so I'd like to improve it

Re: [Libmesh-devel] [Libmesh-users] System::read_serialized_data performance

2012-10-06 Thread Roy Stogner
On Sat, 6 Oct 2012, David Knezevic wrote: > I agree, I think we do need a specialized I/O implementation that > concatenates vectors. The key parts of the RB code related to this are > at line 873 and 940 of rb_evaluation.C. We currently write (or read) a > bunch of vectors one after the other, b

Re: [Libmesh-devel] [Libmesh-users] System::read_serialized_data performance

2012-10-06 Thread David Knezevic
On 10/06/2012 09:59 PM, Roy Stogner wrote: > > On Sat, 6 Oct 2012, David Knezevic wrote: > >> I agree, I think we do need a specialized I/O implementation that >> concatenates vectors. The key parts of the RB code related to this are >> at line 873 and 940 of rb_evaluation.C. We currently write (o

Re: [Libmesh-devel] [Libmesh-users] System::read_serialized_data performance

2012-10-06 Thread Derek Gaston
This seems like the right way to go. Starting to add HDF5 support isn't a bad idea anyway... Derek Sent from my iPhone On Oct 6, 2012, at 7:59 PM, Roy Stogner wrote: > > On Sat, 6 Oct 2012, David Knezevic wrote: > >> I agree, I think we do need a specialized I/O implementation that >> concate