<html><body>Nice I will remember that <i><br><br>On 06/10/13 04:23:30,<br>Ed Kapitein <ed@kapitein.org> wrote:<br></i><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(200, 200, 200); padding-left: 1ex;">
<div class="moz-cite-prefix">I am running one node of the testgrid
on a pi, without any problems.<br>
One of the things that might kill your pi is the oomkiller.<br>
I had numerous ocasions where the oomkiller did not kill a job,
but froze the pi itself.<br>
adding the following lines to /etc/sysctl.conf<br>
vm.overcommit_memory = 2<br>
vm.overcommit_ratio = 80<br>
made the crashes go away.<br>
<br>
Just my 0.02 BTC<br>
<br>
Kind regards,<br>
Ed<br>
<br>
<br>
On 10/06/13 04:07, Garonda Rodian wrote:<br>
</div>
<blockquote cite="mid:COL125-W3745C1455B4FE715CAA379C0120@phx.gbl"
type="cite">
<style><!--
hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">Very interesting - your grid looks to have been up
for 2 days now :). I had investigated the BeagleBone Blacks,
but eventually decided that on paper the Raspberry Pi was a
better very low end platform (2 USB host ports vs. 1 was more
important to me than the BBB's better CPU and lower power draw)
and was a bit cheaper, and the ODROID-U2 was a better low end
platform (quad core ARM + 2GB RAM, still 2 USB host ports, still
100Mbps Ethernet but at least it's not on the USB bus anymore).<br>
<br>
Did you check the Raspberry Pi's on-board voltage at the time of
the brownouts/crashes, or can you help with with whatever test
case crashed it, so I can check on that myself?<br>
<br>
<br>
<div>
<hr id="stopSpelling">From: <a class="moz-txt-link-abbreviated" href="mailto:jason.johnson@p7n.net">jason.johnson@p7n.net</a><br>
To: <a class="moz-txt-link-abbreviated" href="mailto:deepside@hotmail.com">deepside@hotmail.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:anders.genell@gmail.com">anders.genell@gmail.com</a><br>
CC: <a class="moz-txt-link-abbreviated" href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
Subject: RE: [tahoe-dev] Precise Puppy (linux) tahoe-lafs
1.10.0 initial report<br>
Date: Fri, 4 Oct 2013 23:23:20 -0700<br>
<br>
<style><!--
ExternalClass .ecxshape {
}
--></style>
<style><!--
ExternalClass p.ecxMsoNormal, .ExternalClass li.ecxMsoNormal, .ExternalClass div.ecxMsoNormal {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
ExternalClass a:link, .ExternalClass span.ecxMsoHyperlink {
color:blue;
text-decoration:underline;
}
ExternalClass span.ecxMsoHyperlinkFollowed {
color:purple;
text-decoration:underline;
}
ExternalClass p {
font-size:12.0pt;
font-family:"Times New Roman","serif";
}
ExternalClass span.ecxEmailStyle18 {
font-family:"Calibri","sans-serif";
color:#1F497D;
}
ExternalClass .ecxMsoChpDefault {
font-size:10.0pt;
}
ExternalClass div.ecxWordSection1 {
}
--></style>
<div class="ecxWordSection1">
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">I
have been using BeagleBone Blacks with debian wheezy. So
far so good the grid is located <a
moz-do-not-send="true"
href="https://tahoe.netgreen.us" target="_blank">https://tahoe.netgreen.us</a>
there is 8 bbb in this grid. PI seemed to brown out or
crash on me during testing. Just thought I would toss
this in incase you wanted to take a look.</span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;">Jason</span></p>
<p class="ecxMsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D;"> </span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in;">
<p class="ecxMsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";">
<a class="moz-txt-link-abbreviated" href="mailto:tahoe-dev-bounces@tahoe-lafs.org">tahoe-dev-bounces@tahoe-lafs.org</a>
[<a class="moz-txt-link-freetext" href="mailto:tahoe-dev-bounces@tahoe-lafs.org">mailto:tahoe-dev-bounces@tahoe-lafs.org</a>] <b>On
Behalf Of </b>Garonda Rodian<br>
<b>Sent:</b> Friday, October 4, 2013 9:11 PM<br>
<b>To:</b> Anders Genell<br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
<b>Subject:</b> Re: [tahoe-dev] Precise Puppy
(linux) tahoe-lafs 1.10.0 initial report</span></p>
</div>
</div>
<p class="ecxMsoNormal"> </p>
<div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";">Thank
you for the feedback, Anders!<br>
<br>
I'm definitely not starting X on the Pi (model B),
though I had not yet lowered the GPU RAM to 16MB.<br>
<br>
Can you give me an idea of what "a bunch of very large
files" means - 100x100MB? 50x10GB? 4x1TB? I can say
I almost always use Sandisk Ultra or Extreme SD cards,
though I was honestly planning on having the storage
be on a USB flash drive, leaving the SD 100% for the
boot drive and OS.<br>
<br>
I was actually hoping to run two storage nodes, with
either two USB flash drives on the same grid, or one
USB flash drive and one USB hard drive, each on
different grids (a "small storage" grid and a "large
storage" grid).<br>
<br>
Back to the original topic, Precise Puppy 5.7.1 on a
physical box, quad core i7 with 4GB of RAM has now
successfully completed one test, 100% local, with two
storage nodes, one Introducer, and on client/Gateway,
once I figured out which ports in the config files are
used for what. Up to a 1GB file was uploaded without
a problem, though it appears that the bottleneck was
the gateway with a CPU bottleneck. Regrettably, it
looks like profiling the Python code will require
altering the python code, so I've got to figure out
how to do that so I can see where the slow point is.<br>
<br>
Does anyone know if it's OK on Debian/Ubuntu to
statically assign ports from the IANA dynamic port
range of 49152 to 65535 if the system is also likely
to assign some dynamic ports? I'm a big fan of
knowing what your ports are, and that'll be critical
once I toss a firewall or two into the mix.</span></p>
<div>
<div class="ecxMsoNormal" style="text-align:center;"
align="center"><span
style="font-family:"Calibri","sans-serif";">
<hr id="ecxstopSpelling" size="2" width="100%"
align="center"></span></div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";">CC:
<a moz-do-not-send="true"
href="mailto:zookog@gmail.com">zookog@gmail.com</a>;
<a moz-do-not-send="true"
href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
From: <a moz-do-not-send="true"
href="mailto:anders.genell@gmail.com">anders.genell@gmail.com</a><br>
Subject: Re: [tahoe-dev] Precise Puppy (linux)
tahoe-lafs 1.10.0 initial report<br>
Date: Fri, 4 Oct 2013 06:43:55 +0200<br>
To: <a moz-do-not-send="true"
href="mailto:deepside@hotmail.com">deepside@hotmail.com</a></span></p>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">Hi
again, sorry for replying so late...</span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">The
Pis used for storage nodes are in general not used
for anything else, and we try to keep X turned off
to save resources. You can also lower the amount
of RAM reserved for the GPU to a minimal 16 Mb in
the config.txt file in the Pi boot partition. </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">Also,
some of our Pis krashed when stressed, e.g. by
uploading a bunch of very large files, until the
SD card was replaced by a Sandisk SDSDX-016G-X46.
The Pi is notoriously sensitive about what card is
being used. </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">Finally,
if lack of memory is limiting performance, it is
possible to set up a swap partition on the Pi. It
will slow things down horribly, of course, but may
just get the job done. </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">Regards,</span></p>
</div>
<div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";">Anders</span></p>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";"> </span></p>
</div>
</div>
<div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";"><br>
28 sep 2013 kl. 05:20 skrev Garonda Rodian <<a
moz-do-not-send="true"
href="mailto:deepside@hotmail.com">deepside@hotmail.com</a>>:</span></p>
</div>
<blockquote style="">
<div>
<div>
<p class="ecxMsoNormal" style=""><span
style="font-family:"Calibri","sans-serif";"><br>
Thank you for the report on the Raspberry Pi
being used in production - are you and your
friends running just one storage node on the
Pi, or are you also running any other software
(second storage node, Tor, I2P, OpenVPN?). My
RPi consistently simply dies during the trial
- no errors, it just... stops, but based on
your feedback, I'll continue.<br>
<br>
As I'm hoping to run some medium scale tests,
I'm going to have to have something to
generate a lot of nodes all at once, and I
hate wasting effort. At this point, I'm
targetting something more like the old
terminal/3270/DOS menus and/or wizards -
simple walkthroughs with questions to answer
that can be used to create the files for an
entire grid, or add to an existing grid's
files, hopefully with some manner of "wrapper"
(Tor, I2P, OpenVPN) capabilities available as
well.<br>
<br>
Does anyone have a good Python tutorial for
experienced programmers? My C and assembly
used to be pretty good and my SQL is
excellent, but I haven't picked up a new
language in a long time, and I never dealt
with parallelization much.<br>
<br>
P.S. the Precise Puppy 5.7.1 VM at 768MB fails
with the GUI, but succeeds at the command line
with everything nonessential (cups printer
daemon) disabled, so the critical memory limit
for the trial is very close to there, OS
overhead included.</span></p>
<div>
<p class="ecxMsoNormal"><span
style="font-family:"Calibri","sans-serif";">>
From: <a moz-do-not-send="true"
href="mailto:anders.genell@gmail.com">anders.genell@gmail.com</a><br>
> Date: Thu, 26 Sep 2013 19:54:44 +0200<br>
> To: <a moz-do-not-send="true"
href="mailto:zookog@gmail.com">zookog@gmail.com</a><br>
> CC: <a moz-do-not-send="true"
href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
> Subject: Re: [tahoe-dev] Precise Puppy
(linux) tahoe-lafs 1.10.0 initial report<br>
> <br>
> <br>
> > <br>
> >> P.S. If I'm lucky, the
Raspberry Pi has completed its trial run,
though if this is the RAM requirement, I'm
not holding out much hope.<br>
> > <br>
> > It is too bad about #1476, because
I really like to be able to run<br>
> > unit tests everywhere and all the
time. However, I believe that the<br>
> > gateway or storage-server itself
will run fine on Raspberry Pi, even<br>
> > if (due to #1476) the tests will
fail.<br>
> > <br>
> > <br>
> <br>
> Just to chime in: We have several
storage nodes running off of RPis in our
friendnet, and they seem to work fine as
such. <br>
> <br>
> We would absolutely love a setup menu -
many of our participating friends have never
used a terminal. Looking forward to be
dazzled!!<br>
> <br>
> Regards,<br>
> Anders<br>
>
_______________________________________________<br>
> tahoe-dev mailing list<br>
> <a moz-do-not-send="true"
href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a><br>
> <a moz-do-not-send="true"
href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev"
target="_blank">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a></span></p>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
tahoe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:tahoe-dev@tahoe-lafs.org">tahoe-dev@tahoe-lafs.org</a>
<a class="moz-txt-link-freetext" href="https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev">https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev</a>
</pre>
</blockquote>
<br>
<blockquote /></body></html>