Hi Peter, I looked into this a while ago and whilst the details escape
me, the config I settled on was the following:
readerQuotas maxDepth=32 maxStringContentLength=2147483647
maxArrayLength=2147483647 maxBytesPerRead=4096
maxNameTableCharCount=2147483647/
Empirically, this allowed me to
Hi Peter,
have you considered streaming (
http://msdn.microsoft.com/en-us/library/ms731913.aspx)? Might be the better
option given the variable file sizes.
Regards,
Steve
On 31 January 2011 09:09, Wallace Turner w.tur...@fex.com.au wrote:
Hi Peter, I looked into this a while ago and
Ok Thanks
It would be nice to know what they actually do and what behaviour they
alter.
If you have maxed out the attribute values and have left maxBytesPerRead
as the default, I would guess its impact at a performance level with the
size of network IO requests. Increase the value for
have you considered streaming
I had heard of it but hadn't gone into the details (thanks for the link).
I think streaming is more for large volumes of data (video and audio
streaming).
My downloads are lots of fairly small files (with some exceptions).
I am leaning towards chunked file
