Stefan Eilemann wrote:
>
> On Tue, May 26, 2009 at 10:11 AM, Bo Lou <[email protected]>
> wrote:
>> i have a relativ big vector to send (1366875 elements), so it cost much
>> time
>> in the for-loop(perhaps). when i used the read & write methods i got the
>> problem as Thomas mentioned. i don't know how to get rid of it & need
>> help.
>
> What is your vector data? If it is strings, or some other non-trivial
> data type, it has to be serialized using the for loop.
>
> When and where do you spend the time? During initial mapping, or
> during commit? Are you network- or CPU-bound?
>
>
> Best,
>
> Stefan.
>
> _______________________________________________
> eq-dev mailing list
> [email protected]
> http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
> http://www.equalizergraphics.com
>
>
Hi Stefan,
thanks for the quick reply. my vector type :
typedef std::vector< unsigned char > DataCharVector;
typedef std::vector< float > DataFloatVector;
the time was spended During initial mapping in the function
getInstanceData();
i test the Programm on my laptop.
Best Regards
Bo Lou
--
View this message in context:
http://n2.nabble.com/Bug-in-DataIStream%3A%3Aoperator-%3E%3E-and-DataOStream%3A%3Aoperator-%3C%3C-tp2290241p2974188.html
Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com.
_______________________________________________
eq-dev mailing list
[email protected]
http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev
http://www.equalizergraphics.com
