Re: Remoting large dataset - deserialization is slow
- From: Spam Catcher <spamhoneypot@xxxxxxxxxx>
- Date: Mon, 06 Nov 2006 10:01:19 GMT
"tanitack" <tanitack@xxxxxxxxx> wrote in news:1162794993.167204.159640
@m7g2000cwm.googlegroups.com:
The buffer size in the above code for which it took 4 secs was
35139484.
Is that 35MB of data?
The code provided in Ingo Rammer's book may not be production ready.
You pointed out that you're transferring approximately 68,000 rows - that
is a huge dataset to be retrieving (let alone remoting!).
Could you page the dataset? Send the data in chunks to the remote client as
they're needed?
Perhaps a dataset may not be the best data type to use - something lighter
weight might be more suitable (a custom data object or an array?).
There's always geniune channels too - which has production ready
compression built in.
.
- Follow-Ups:
- Re: Remoting large dataset - deserialization is slow
- From: tanitack
- Re: Remoting large dataset - deserialization is slow
- References:
- Remoting large dataset - deserialization is slow
- From: tanitack
- Remoting large dataset - deserialization is slow
- Prev by Date: Remoting large dataset - deserialization is slow
- Next by Date: Re: Remoting large dataset - deserialization is slow
- Previous by thread: Remoting large dataset - deserialization is slow
- Next by thread: Re: Remoting large dataset - deserialization is slow
- Index(es):