Plus with more RAM .... in the cards?
#1
Posted 05 February 2012 - 09:53 PM
#2
Posted 05 February 2012 - 10:02 PM
I was having the same troubles until I saw this thread.
Re: memory pig
So I changed my code around and now I rarely get out of memory exceptions.
Hope you find it helpful.
#3
Posted 06 February 2012 - 12:33 AM
I was having the same troubles until I saw this thread.
Re: memory pig
It is helpful, but does not apply, I think...
My memory problems flow from the use of this code:
http://forums.netdui...dpost__p__23637
This code already uses FileStream, and has no use of StreamReader...
Any other ideas?
#4
Posted 06 February 2012 - 09:30 AM
#5
Posted 06 February 2012 - 02:47 PM
Lose the WebRequest. Internally it uses StreamReader. That's why, in the post mentioned above, my other sample shows direct use of a socket.
(In, in your other post I focused on the use of IO to the SD card, and reviewed my own, and found no streams... I misunderstood!)
Ohhhh, I am loath to lose WebRequest. It works reliably, and helps me keep my code really simple. It lets me do stuff like http://100.200.50.25.../path/endpoiint really easily. With Sockets, the implementations all had various limitations (assuming port 80, etc etc).
I have used sockets, but really am glad to have moved away from them (in fact, a broken WebRequest implementation is why I left the Panda platform and came back to netduino).
Is there a full socket implementation for http GET?
#6
Posted 06 February 2012 - 11:12 PM
No, there isn't. I have been toying with the idea of getting NETMF and modifying it to reduce the internal buffer allocations of StreamReader. Without WebRequest it's waaaaay too much work to use SSL, for example.Is there a full socket implementation for http GET?
#7
Posted 06 February 2012 - 11:38 PM
No, there isn't. I have been toying with the idea of getting NETMF and modifying it to reduce the internal buffer allocations of StreamReader. Without WebRequest it's waaaaay too much work to use SSL, for example.
Sounds like I am on the same page with you:
WebRequest is just too useful, and there isn't a good drop in replacement for it.
Over on the Panda side, I spent hours and hours (20, I think, and that is expensive for me as a hobbyist), discovering that their implementation of WebRequest was so buggy to be unusable. I used sockets because that was all that would work, but found I was spending all my time managing/enhancing socket based code, and not spending time on my actual project.
I came back to netduino specifically to have working WebRequest, and am now hitting the memory wall because Netduino + is so very memory constrained due small available memory on the chip + overhead of networking code.
Open to all suggestions!
#8
Posted 08 February 2012 - 12:10 AM
#9
Posted 08 February 2012 - 02:51 AM
#10
Posted 08 February 2012 - 03:33 AM
#11
Posted 08 February 2012 - 04:10 AM
BTW, have you noticed how much free RAM is available on Netduino Plus with .NET MF 4.2 RC4 firmware?
Not yet. I fear I don't have time until 4.2 goes gold (as a hobbyist my time is very constrained).
#12
Posted 08 February 2012 - 12:55 PM
#13
Posted 08 February 2012 - 02:04 PM
As soon as the community lets us know that things are stable, we'll be pushing 4.2 beyond beta. It sounds like the latest release candidate really helped on the stability front, so we're optimistic that it'll be within the next two months.Got a rough guesstimate of when 4.2 might go gold? I realise this is a how-long-is-a-piece-of-string question.
Chris
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users