<div><div>Thank you so much for the detailed insight and the metrics, Tony.<br></div><div>All of this information will be extremely valuable for me while thinking of my proposal.<br></div><div>I'll dive into workload characterization and keep you posted as this is of interest to you, thank you so much for your time :)<br></div><div><div><br></div></div><div>Rishabh.<br></div></div><div><br></div><div>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<br></div><div> On March 3, 2018 9:33 AM, Tony Anderson <tony_anderson@usa.net> wrote:<br></div><div> <br></div><blockquote class="protonmail_quote" type="cite"><div class="moz-cite-prefix"><div>This is exactly how the xsce server
works so you may get valuable help from that community (xsce or
iiab). <br></div><div> <br></div><div> A continuing issue is performance of the server in a classroom or
school. One metric is the number of simultaneous connections the
device can support (a classroom of 40-60 is not uncommon).
Response time to requests to the server can be limited by the size
of memory, the speed of access to the sd card, or the processor
speed. I would be very interested in the methodology you propose
since that process would apply equally to the schoolserver. <br></div><div> <br></div><div> One issue is to characterize the workload - how often does a user
request a transaction from the server, what is the time between
requests (when the user is reading the response to the previous
request), how much processing is required for a request (e.g. a
text search), how much information is required to satisfy a
request (e.g. size of file download). So far as I know no one has
attempted this characterization for a classroom. This load could
be different for Sugarizer than for Sugar, but the effort would be
valuable in any case).<br></div><div> <br></div><div> Tony<br></div><div> <br></div><div> On Friday, 02 March, 2018 11:16 PM, Rishabh Nambiar wrote:<br></div></div><blockquote type="cite"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;" id="docs-internal-guid-0e43a464-e7d5-d3af-2723-9d4cb2d2bcc5"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt">Hi everyone, <br> I had a quick chat with Michaël about moving forward
with this GSoC project where he mentioned that the
impact of the project should be discussed with the
community:</span></span></span></span></p><div dir="ltr"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt"></span></span></span></span><br></div><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a href="http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html" style="text-decoration:none;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(17, 85, 204)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt"><u>http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html</u></span></span></span></span></a><br></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><a href="http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html" style="text-decoration:none;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(17, 85, 204)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt"><u>http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html</u></span></span></span></span></a><br></p><h2 dir="ltr" style="line-height:1.38;margin-top:18pt;margin-bottom:6pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><b><span class="font" style="font-family:Arial"><span class="size" style="font-size:16pt">Impact of the Sugarizer School
Box</span></span></b></span></span><br></h2><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt">An instructor walks into a
classroom, equipped with a Raspberry Pi 3 or Zero W with
a pre-installed version of the proposed Sugarizer School
Box distribution that Sugar Labs will be working on.<br class="kix-line-break"> He/she simply connects the Pi to a power supply and
instantly, a local WiFi network is set up, a Sugarizer
server session starts automatically and they’re ready to
go! <br class="kix-line-break"> <br class="kix-line-break"> </span></span><span class="size" style="font-size:11pt"><span class="font" style="font-family:arial, sans-serif">Students
can log in to the WiFi AP made by the Pi and visit
sugarizer.org (any other fixed url) on their local
tablets/laptops/phones. So any computer connected to
this WiFi can use the Sugarizer client and any
tablet/phone with Sugarizer apps will benefit from the
collaboration and backup features on the server. All of
these student devices will be served by the Pi Wifi AP.</span></span></span></span></p><h3 dir="ltr" style="line-height:1.38;margin-top:16pt;margin-bottom:4pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(67, 67, 67)"><b><span class="font" style="font-family:"Helvetica Neue""><span class="size" style="font-size:14pt">Issues</span></span></b></span></span><br></h3><h4 dir="ltr" style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(102, 102, 102)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:12pt">Processing Power</span></span></span></span><br></h4><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt">We’ll have to see how the Pi’s
can cope with the load of serving multiple students
along with the overhead of running a browser session for
a client and the connected display.<br class="kix-line-break"> I have a Raspberry Pi B+ and a Pi Zero W at my disposal
that I can use to test this so I’ll post the results of
combining sugarizer-server and a WiFi AP soon. It should
do the job as we will not be having too many students on
one Pi.</span></span></span></span></p><h4 dir="ltr" style="line-height:1.38;margin-top:14pt;margin-bottom:4pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(102, 102, 102)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:12pt">Network Limitations</span></span></span></span><br></h4><div dir="ltr"><span class="highlight" style="background-color:transparent"><span class="font" style="font-family:arial, sans-serif"><span class="colour" style="color:rgb(34, 34, 34)"><span class="size" style="font-size:14px">It's a straightforward process
to set up a local AP for the Pi with the
sugarizer-server running but if there is a need for
Internet connectivity, then we'll have to set up an
Ethernet bridge to make this possible which is also not
very complicated.</span></span></span><span class="font" style="font-family:Arial"><span class="colour" style="color:rgb(102, 102, 102)"><span class="size" style="font-size:14px"><br> </span><span class="size" style="font-size:12pt"><br> </span><b><span class="size" style="font-size:12pt">UX</span></b></span></span></span></div><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:arial, sans-serif"><span class="size" style="font-size:14px">The setup process in a classroom
should ideally just be connecting the Pi to a power
supply. <br> Minor UX features like an auto-redirect to sugarizer.org
after connecting to the WiFi AP can be implemented</span></span><span class="font" style="font-family:Arial"><span class="size" style="font-size:14px">. </span></span></span></span></p><div dir="ltr"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><span class="size" style="font-size:11pt"></span></span></span></span><br></div><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;"><span class="highlight" style="background-color:transparent"><span class="colour" style="color:rgb(0, 0, 0)"><span class="font" style="font-family:Arial"><b><span class="size" style="font-size:16px">If anyone from the community
has any opinions or concerns about how any part of the
School Box experience should be, then that’d be
awesome.</span></b></span></span></span><span class="size" style="font-size:16px"><br> </span><span class="size" style="font-size:14px"><br> </span><span class="size" style="font-size:14px">Regards, </span><span class="size" style="font-size:14px"><br> </span><span class="size" style="font-size:14px">Rishabh
Nambiar.</span><span class="size" style="font-size:14px"></span></p><div><br></div><div><br></div><div><br></div><pre wrap="">_______________________________________________
Sugar-devel mailing list
<a href="mailto:Sugar-devel@lists.sugarlabs.org" class="moz-txt-link-abbreviated">Sugar-devel@lists.sugarlabs.org</a>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" class="moz-txt-link-freetext">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
<br></pre></blockquote><p><br></p></blockquote><div><br></div>