Re: [Sugar-devel] Impact of the Sugarizer School Box | Rishabh Nambiar |

[Rishabh Nambiar]

That's great, I'll keep an eye out for the release and we should definitely 
include Turtle/Music Blocks! :)

-Rishabh
‐‐‐ Original Message ‐‐‐
On March 4, 2018 8:30 PM, Walter Bender  wrote:

> Might be nice to include an instance of the Turtle/Music blocks server as 
> well. We are preparing a new release of the server/clients over the next few 
> days.
>
> -walter
>
> On Sat, Mar 3, 2018 at 3:51 PM, Rishabh Nambiar  
> wrote:
>
>> Thank you so much for the detailed insight and the metrics, Tony.
>> All of this information will be extremely valuable for me while thinking of 
>> my proposal.
>> I'll dive into workload characterization and keep you posted as this is of 
>> interest to you, thank you so much for your time :)
>>
>> Rishabh.
>>
>> ‐‐‐ Original Message ‐‐‐
>> On March 3, 2018 9:33 AM, Tony Anderson  wrote:
>>
>>> This is exactly how the xsce server works so you may get valuable help from 
>>> that community (xsce or iiab).
>>>
>>> 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.
>>>
>>> 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).
>>>
>>> Tony
>>>
>>> On Friday, 02 March, 2018 11:16 PM, Rishabh Nambiar wrote:
>>>
 Hi everyone,
 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:

 http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html

 http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html

 Impact of the Sugarizer School Box

 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.
 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!

 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.

 Issues

 Processing Power

 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.
 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.

 Network Limitations

 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.

 UX

 The setup process in a classroom should ideally just be connecting the Pi 
 to a power supply.
 Minor UX features like an auto-redirect to sugarizer.org after connecting 
 to the WiFi AP can be implemented.

 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.

 Regards,
 Rishabh Nambiar.

 __

 _
 Sugar-devel mailing list
 [Sugar-devel@lists.sugarlabs.

 org](mailto:Sugar-devel@lists.sugarlabs.org)

 [http://lists.sugarlabs.org/

 listinfo/sugar-devel](http://lists.sugarlabs.org/listinfo/sugar-devel)
>>
>> 

Re: [Sugar-devel] Impact of the Sugarizer School Box | Rishabh Nambiar |

[Walter Bender]

Might be nice to include an instance of the Turtle/Music blocks server as
well. We are preparing a new release of the server/clients over the next
few days.

-walter

On Sat, Mar 3, 2018 at 3:51 PM, Rishabh Nambiar 
wrote:

> Thank you so much for the detailed insight and the metrics, Tony.
> All of this information will be extremely valuable for me while thinking
> of my proposal.
> I'll dive into workload characterization and keep you posted as this is of
> interest to you, thank you so much for your time :)
>
> Rishabh.
>
> ‐‐‐ Original Message ‐‐‐
> On March 3, 2018 9:33 AM, Tony Anderson  wrote:
>
> This is exactly how the xsce server works so you may get valuable help
> from that community (xsce or iiab).
>
> 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.
>
> 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).
>
> Tony
>
> On Friday, 02 March, 2018 11:16 PM, Rishabh Nambiar wrote:
>
> Hi everyone,
> 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:
>
> *http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html*
> 
>
> *http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html*
> 
> *Impact of the Sugarizer School Box*
>
> 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.
> 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!
>
> 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.
> *Issues*
> Processing Power
>
> 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.
> 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.
> Network Limitations
> 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.
>
> *UX*
>
> The setup process in a classroom should ideally just be connecting the Pi
> to a power supply.
> Minor UX features like an auto-redirect to sugarizer.org after connecting
> to the WiFi AP can be implemented.
>
> *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.*
>
> Regards,
> Rishabh Nambiar.
>
>
>
> ___
> Sugar-devel mailing 
> listSugar-devel@lists.sugarlabs.orghttp://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Impact of the Sugarizer School Box | Rishabh Nambiar |

[Rishabh Nambiar]

Thank you so much for the detailed insight and the metrics, Tony.
All of this information will be extremely valuable for me while thinking of my 
proposal.
I'll dive into workload characterization and keep you posted as this is of 
interest to you, thank you so much for your time :)

Rishabh.

‐‐‐ Original Message ‐‐‐
On March 3, 2018 9:33 AM, Tony Anderson  wrote:

> This is exactly how the xsce server works so you may get valuable help from 
> that community (xsce or iiab).
>
> 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.
>
> 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).
>
> Tony
>
> On Friday, 02 March, 2018 11:16 PM, Rishabh Nambiar wrote:
>
>> Hi everyone,
>> 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:
>>
>> http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html
>>
>> http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html
>>
>> Impact of the Sugarizer School Box
>>
>> 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.
>> 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!
>>
>> 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.
>>
>> Issues
>>
>> Processing Power
>>
>> 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.
>> 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.
>>
>> Network Limitations
>>
>> 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.
>>
>> UX
>>
>> The setup process in a classroom should ideally just be connecting the Pi to 
>> a power supply.
>> Minor UX features like an auto-redirect to sugarizer.org after connecting to 
>> the WiFi AP can be implemented.
>>
>> 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.
>>
>> Regards,
>> Rishabh Nambiar.
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>>
>> http://lists.sugarlabs.org/listinfo/sugar-devel___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Impact of the Sugarizer School Box | Rishabh Nambiar |

[Tony Anderson]

This is exactly how the xsce server works so you may get valuable help 
from that community (xsce or iiab).


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.


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).


Tony

On Friday, 02 March, 2018 11:16 PM, Rishabh Nambiar wrote:


Hi everyone,
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:



_http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html_

_http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html_


*Impact of the Sugarizer School Box*

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.
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!


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.



  *Issues*


Processing Power

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.
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.



Network Limitations

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.


*UX*

The setup process in a classroom should ideally just be connecting the 
Pi to a power supply.
Minor UX features like an auto-redirect to sugarizer.org after 
connecting to the WiFi AP can be implemented.



*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.*


Regards,
Rishabh Nambiar.




___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel



___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Impact of the Sugarizer School Box | Rishabh Nambiar |

[Rishabh Nambiar]

Hi everyone,
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:

http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055078.html

http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055079.html

Impact of the Sugarizer School Box

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.
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!

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.

Issues

Processing Power

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.
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.

Network Limitations

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.

UX

The setup process in a classroom should ideally just be connecting the Pi to a 
power supply.
Minor UX features like an auto-redirect to sugarizer.org after connecting to 
the WiFi AP can be implemented.

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.

Regards,
Rishabh Nambiar.___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel