Changes

Jump to navigation Jump to search
696 bytes removed ,  15:04, 22 March 2018
m
Line 244: Line 244:     
====Setting up a Development Environment====
 
====Setting up a Development Environment====
:I wasn’t sure if this project falls under the Sugar-Web projects or the Sugar projects.
+
 
 +
:I wasn’t sure if this project falls under the Sugar-Desktop projects or the Sugar Web projects so for a relevant screening task, you can check a Sugarizer deployment I’ve done at http://rishabhn.xyz:8080/
 +
 
 
:I've deployed Sugarizer on my Raspberry Pi 3 and a VPS with Docker and without it.
 
:I've deployed Sugarizer on my Raspberry Pi 3 and a VPS with Docker and without it.
 
:It works really well and I haven’t run into any major issues.
 
:It works really well and I haven’t run into any major issues.
  −
:
  −
[[File:Locustsugarizersmaller.png|center]]
  −
:
  −
  −
  −
====Workload Analysis for sugarizer-server====
  −
:I've been testing the page load times for some activities using Locust, a user load testing tool written in Python that lets you test site performance by swarming it with users.
  −
:This will fulfill one of the tasks in the node.js performance analysis of sugarizer-server which lets us know the size of the file download per page/activity and response times as the number of users increases.This analysis will be important when I run them on the Raspberry Pi WiFi AP along with the other tasks in parallel. I will try to replace this section with a more complete analysis as soon as possible.
  −
  −
:''PS:'' ''This screenshot is not a good indicator of real-world performance because:''
  −
::* 300 users
  −
::* 30 requests/second
      
====Describe a great learning experience you had as a child.====
 
====Describe a great learning experience you had as a child.====

Navigation menu