Archived
This forum has been archived. Please start a new discussion on GitHub.
Performance of ice marshal and unmarshal
in Help Center
I am looking into the performance of ice's marshal and unmarshal of parameters.
Server is a data center, only one query of client, server may return a great amount of data, usually 1M~50M. If I define such remote call based on slice(see sequences), server will consume terrible memory when marshaling or unmarshaling.
I have study BasicStream of ice, it seems that ice can not marshal or unmarshal until ice allocate memory of total package size. In face, memory uesd on marshal and unmarshal is twice or three times of package size.
Think, ten or more clients query such large data at the same time, the memoy used on marshal or unmarshal is not be accepted absolutely.
Does any body have any good idea of solving this problem.
Server is a data center, only one query of client, server may return a great amount of data, usually 1M~50M. If I define such remote call based on slice(see sequences), server will consume terrible memory when marshaling or unmarshaling.
I have study BasicStream of ice, it seems that ice can not marshal or unmarshal until ice allocate memory of total package size. In face, memory uesd on marshal and unmarshal is twice or three times of package size.
Think, ten or more clients query such large data at the same time, the memoy used on marshal or unmarshal is not be accepted absolutely.
Does any body have any good idea of solving this problem.
0
